Check website availability
from 30+ locations worldwide
See whether your site loads in each city, how long it takes there, and what is making it slow. Every checkpoint uses a real Chrome browser.
What the test shows you
Whether your site loads
30+ locations load your page at the same time, from New York to Tokyo. You see whether the problem is everywhere, in one region, or only on your own connection.
How fast it loads
Time to first byte and download time for every location, plus Core Web Vitals, a performance score and a list of what to fix first.
A link you can share
Every test gets its own link, screenshots and a status badge you can embed. The link stays live for 7 days.
How the test runs
Enter any URL
No account, no email, no credit card. We keep the host and the path and drop the query string, so nothing private is stored or shared.
30+ locations load your page
Each checkpoint looks up your DNS locally, opens its own connection, follows any redirects and downloads the whole page: HTML, images, fonts and scripts. Cities report back as they finish.
Read the results
Up or down per city, the timing behind each load, Core Web Vitals and a list of what to improve. Share the link with your team.
What the report contains
Every part of the report comes from the same test run. Here is what each part shows.
Results for every location
The map colours each checkpoint that answered: green loaded fine, amber was slow, red failed. The table below it gives you the numbers, and the region tabs let you compare one continent with the rest.
- First byte and total time per city — the bar splits the wait into waiting for your server and downloading the page
- Slow is measured against this test — a city is compared with the median of your own run, so distance alone never flags it
- Fastest and slowest city — both are named at the top of the report, with their load times
| Location | Timing breakdown | First byte | Total |
|---|---|---|---|
| Frankfurt DE | 98 ms | 0.82 s | |
| London GB | 112 ms | 0.94 s | |
| New York US | 186 ms | 1.31 s | |
| São Paulo BR | 402 ms | 2.04 s | |
| Tokyo JP | 315 ms | 3.41 s |
Where the time goes
One bar shows whether the page is slow because your server was slow to answer, or because of what it sent back. The Core Web Vitals and the suggested fixes sit underneath it.
- Server or assets — a long first byte points to your server, a long download points to the page itself
- Core Web Vitals — largest paint, layout shift and server response time, each compared with Google's threshold
- Fixes in order of impact — each one shows the time or the kilobytes it would save
hero.jpg and 6 others are still JPEG
2 stylesheets delay the first paint
Screenshots and a shareable link
A status code only tells you the server answered. The screenshot shows whether the page actually appeared. Both are in the report, along with a link you can send to someone else.
- Desktop and mobile screenshots — what Chrome displayed at each screen width
- A link that stays live for 7 days — send it to your host, a client or a colleague; no account needed
- Status badge and history — an image you can embed, and a chart of earlier tests of the same site
What a failed check means
Where the failures appear tells you what is wrong:
The problem is at your site, not on the way to it: DNS that does not resolve, a server refusing connections, or a certificate the browser rejects.
Something between your site and that region: a CDN location serving errors, a country block, or a firewall rule dropping that traffic. The report names the region.
We leave it out of the result. One failure among ten or more successful loads is a problem with that checkpoint, not with your site. Two or more failures are always shown.
Those requests are travelling a long way to reach your server. Nothing is cached near those visitors. A CDN, or a server closer to them, fixes it.
Distance cannot explain a delay that also happens nearby. Time before the first byte is your application: database queries, empty caches, or an overloaded server.
Your DNS cache, a VPN, an office proxy or a browser extension is between you and a site that is up. Check your own connection first.
What the numbers mean
Every timing in the report measures part of one page load:
- Time to first byte
- The DNS lookup, the secure connection and your server's response time, up to the first byte of the page. Everything before the browser has anything to show.
- Download & render
- The rest of the load: images, fonts and scripts arriving, and the browser displaying them.
- Total load
- Both parts added together: what a visitor in that city waits.
- Slow
- A location is marked slow when it takes more than twice the median load time of your test, or more than 8 seconds. Distance on its own never marks a city slow.
- Availability
- A checkpoint counts as available when it gets a successful response and finishes loading the page. A slow location still counts as available.
- Faster than X%
- How this load time compares with every other site tested here in the last 90 days.
- LCP
- Largest Contentful Paint: when the biggest element on the screen finished loading. Google counts 2.5 seconds or less as good.
- CLS
- Cumulative Layout Shift: how much the page moved around while loading. Under 0.1 is good.
- Performance grade
- The Google PageSpeed score for the desktop version of the page, from 0 to 100.
- Page size & requests
- How many bytes were downloaded and how many separate files, taken from the location that saw the most.
Common questions
Your ISP, DNS cache or corporate proxy can serve you a working copy while the rest of the world sees a failure. Testing from 30+ independent locations takes your own network out of the equation. If most checkpoints fail, the problem is on the site's side.
Completely free, no sign-up needed. Uptimia sells continuous monitoring subscriptions, and the free test is how we introduce it.
Each checkpoint runs a real Chrome browser, resolves your DNS, opens a TLS connection and downloads the full page. A location counts as available when the page returns a successful HTTP response and finishes loading.
A ping only proves the server answers ICMP. This test loads your page the way a visitor's browser does: DNS, TLS certificates, redirects, every asset. Broken CDNs, expired certificates and slow origins all show up — a ping misses every one.
Each checkpoint loads the URL as a normal visitor with no cookies, so a page behind a login is reported as the login screen it redirects to. A page restricted to certain IP addresses or countries fails from every checkpoint that is blocked, which is also how you can confirm a country block works.
Every checkpoint has its own network connection, and any of them can have a bad minute. One failure among ten or more successful loads is treated as a problem with that checkpoint and left out of the result. Two or more failures are always shown.
Each checkpoint loads the page in a real Chrome browser with scripts running, so a test can appear as visits in analytics tools that count page views. One test is one visit per location that reports back.
Seven days, at its own link, together with its screenshots. Anyone you send the link to can open it. After seven days the test and its files are deleted. The link contains no query string: we store the host and the path only.
Up to 10 tests per hostname per day. If you need the site checked continuously instead of once, that is what the paid plans do, from the same network of checkpoints.
Yes — that's what Uptimia does. Paid plans check as often as every 30 seconds from the same probe network. When a check fails you're alerted by email, SMS, Slack and nine other channels. Setup takes two minutes. The 30-day trial needs no card, and after it the free plan keeps one site checked every 5 minutes.
Gli strumenti gratuiti sono solo l'inizio.
Uptimia si prende cura dei tuoi siti.
Uptime, SSL, scadenza dominio, velocità delle pagine, transazioni — monitorati da 171+ punti in tutto il mondo. Gratis per 30 giorni.