Speed is not the story.
Every other test hands you a big number and leaves. This one measures what actually decides whether your connection feels good — latency while the line is busy, jitter, the kind of NAT you're stuck behind, which DNS resolvers your network really lets through, and how far you sit from the rest of the world. Then it grades it honestly and tells you the one thing worth fixing.
A line can be fast and still stutter. We watch what happens to your ping while the connection is working hard — the thing that actually ruins calls and games.
A to F, weighted for what you actually do. A weak spot drags the whole grade down, because that is how it feels in real life.
We time a real datacentre on every continent, so you can see whether your provider carries you well beyond its own network.
Your NAT type, whether you are stuck behind carrier-grade NAT, and which DNS servers your own network quietly blocks.
DNS is the internet's phone book. Every time you open a site, your device first has to ask somebody “what is the address for netflix.com?” That somebody is your resolver. Unless you have changed it, it is a machine belonging to your internet provider, and it sees the name of every single site anyone in your house visits.
It does not change your megabits at all. Your line is exactly as fast either way. What it changes is the wait before the download starts — and there is a real difference between those two things.
A page is not one file. A news site is typically 40–80 separate names: the site itself, its images, three fonts, an analytics script, a video player, six advert networks. Each unfamiliar name costs one round trip to your resolver before a single byte of it can be downloaded. At 8 ms nobody notices. At 150 ms the same page spends several seconds doing nothing but asking questions, on a connection that is measuring a perfect gigabit. That is precisely the “my internet is fast but everything feels slow” complaint.
And yes — a blocking resolver can be slower, and can break things. A resolver like AdGuard checks each name against a blocklist first, which adds a little work, and it usually sits in fewer cities than Cloudflare or Google, so it is often further away. That is the price. In return, adverts and trackers never load at all on every device in the house — the TV, the console, the guest phone — which usually makes pages finish sooner overall, because the adverts they cancel were far heavier than the lookups they added. The genuine cost is different: filtering occasionally blocks something you actually wanted, and the fix is never obvious, because a blocked site does not say “blocked”, it just fails. That is a real tradeoff and only you can make it.
A leak means your lookups are reaching a resolver you did not choose — nearly always your provider's. Nothing is stolen and nothing breaks. What happens is that a full list of every site your household visits, with timestamps, accumulates somewhere you have no visibility into. In several countries that list is retained by law and sold or handed over. Whether that bothers you is a personal call; the point of this page is that you get to make it deliberately instead of by default.
The other half is ECS (EDNS Client Subnet). Some resolvers attach part of your address to every question they forward, so the servers being asked learn roughly where you are even when you never visited them. It exists for a good reason — it helps send you to a nearby server — but it does leak location. We check for it below.
Every one of these is a real datacentre, timed one at a time during your test — not an estimate from your address. Two things make it worth reading. The first is that it is the honest floor on anything you do in that part of the world: if a game server, a broker or a colleague sits there, you can never be quicker than the number shown, and no plan you buy changes it, because it is the speed of light through glass. The second is what the SHAPE tells you. A provider that carries you well to its own region and badly everywhere else looks fine on an ordinary speed test and feels wrong all day — that is a routing problem, it is real, and this chart is where it becomes visible.