Ping / latency check
Measure round-trip time from your browser to three well-known servers.
Click Start test to measure round-trip time to three well-known servers. 10 samples per target.
Measurements are HTTP load time, not ICMP ping — numbers will be
slightly higher than a command-line ping, but relative
differences are accurate. A 5000 ms reading means the request
timed out (the target is unreachable or heavily slow).
About this tool
Measure round-trip time from your browser to three well-known servers — Google, Cloudflare, and GitHub — with 10 samples each. Because browsers don't have access to raw ICMP, the measurement is HTTP image load time, so numbers will run slightly higher than a command-line ping. The useful signal is the comparison: if all three are slow, your connection is the problem; if one is slow and the others are fine, that specific network is the problem. A 5000 ms bar means the request timed out.
How to use this tool
-
Click Start
The test fires 10 samples each to Google, Cloudflare, and GitHub — three of the largest networks on the internet, each on different infrastructure.
-
Wait for the bars to settle
The chart updates live as samples land. Final min/avg/max/median numbers appear after about ten seconds, once all 30 probes complete.
-
Compare the three hosts
If all three are slow, the bottleneck is your local connection. If one is slow and the others are fine, the problem is that specific network or the path between you and it.
Frequently asked questions
Why is this different from command-line <code>ping</code>?
Browsers can't send raw ICMP packets (the kernel-level protocol ping uses), so this tool measures HTTP image load time instead. That includes the TLS handshake, any server-side processing, and image decode — so readings will be noticeably higher than ICMP ping. But relative differences between targets and whether a target is reachable at all are still meaningful.
Why these three sites?
They each sit on a different major CDN / network (Google, Cloudflare, and Azure via GitHub), are globally distributed, serve a tiny favicon reliably, and allow cross-origin image loads. Testing all three gives you a rough picture of internet-wide responsiveness from your browser right now.
What does a 5000 ms bar mean?
That the request timed out — we cap each sample at five seconds so the test doesn't hang. Common causes: the target is genuinely unreachable from your network, a browser extension or firewall is blocking it, or the network is badly congested. Try again, or check the other targets to see if it's specific to one site.
Why are these numbers higher than command-line ping?
Browsers don't have access to ICMP, so the measurement is the time to load a 1×1 image over HTTPS. That includes TLS handshake overhead and connection setup that ping skips. Expect numbers ~20-40 ms higher than a CLI ping to the same host.
What counts as good vs bad latency?
Under 50 ms is excellent — typical of fibre or cable on the same continent. 50-150 ms is normal across an ocean. Above 200 ms is sluggish for interactive work (SSH, video calls). Above 500 ms there's almost always a problem.