Bandwidth is what you pay for. Access is what you get.
No remote servers — every millisecond below was measured from your device.
A traditional speed test asks: “How fast is my line?”
It measures bandwidth to a test server someone else picked, usually a few miles away. A big number, and no answer to whether the sites you opened this morning actually load.
We ask: “How fast are my sites — from this device?”
Every row below is a real request to a real site, timed from where you are right now. Same line, same minute — and you can see which of them answer, and which don't.
Each row is a real HTTP request sent from your browser, timed with performance.now(). The clock starts when the request leaves and stops the moment your browser sees a response — that is the site's response time from your connection. We never read the page body, so this is not a measure of how heavy a page is, only of how quickly the site answers.
A web page cannot send an ICMP ping, and browsers don't expose DNS, TCP or TLS timings. So there is no “ping” number here — only end-to-end response time. That still answers the practical question, and it is comparable: same machine, same minute, different sites.
Fast is under 400 ms, OK under 1200 ms, Slow under 3000 ms. A site that answers at or above 3000 ms is marked Very slow — it works, but you will feel it. Unreachable means no response arrived before the timeout; it is never used for a site that answered.
Some sites answer automated-looking requests with a bot check instead of the page — a 403, or a challenge that never finishes. If a site you know works shows as Unreachable, hit Retest, or open it once in a tab and try again.
Everything runs in this page. Results are never sent anywhere — copying or sharing them is the only way they leave, and you choose that. One request goes out to api.ipify.org to label the center node with your public IP; the report hides it unless you tick “Include my public IP”.
SITE SPEED CHECK — REPORT