Ping test
This tool measures Hypertext Transfer Protocol response latency from your browser to a few endpoints. It is labeled as a Hypertext Transfer Protocol ping because browsers cannot send classic Internet Control Message Protocol ping packets.
Results are estimates for information only. Privacy · Terms · Guides
HTTP latency
Click Run to measure HTTP latency.
HTTP latency, not ICMP ping
Classic command-line ping uses ICMP packets. Browsers cannot send those freely, so this tool measures HTTP response latency from your browser to a few endpoints and labels the result as an HTTP ping.
Numbers include network delay plus TLS and server handling. They are useful for relative comparison, not as a pure wire RTT.
Getting a clearer reading
Run the test on a stable connection, close heavy downloads, and retry once or twice. Spikes often come from Wi‑Fi interference, VPN overhead, or a cold connection—not from the page alone.
This is not a download/upload speed test. Pair it with the connection tool for browser-reported link hints and the IP tools to see which path you are on.
Get your related information
Frequently Asked Questions
What is a ping test?
A classic ping measures round-trip time with Internet Control Message Protocol packets. In the browser we measure Hypertext Transfer Protocol latency instead, how long requests take to reach our endpoints, because web pages cannot send Internet Control Message Protocol ping.
Is this the same as command-line ping?
No. Command-line ping uses Internet Control Message Protocol. We measure how long Hypertext Transfer Protocol requests take, which is still useful for rough latency.
What affects the latency numbers?
Distance to the server, your Wi‑Fi or cellular quality, Virtual Private Network overhead, and temporary congestion can all raise latency. One run is a snapshot, not a guarantee.
How do I get a more useful reading?
Run the test a few times on a stable network, pause large downloads, and compare with and without a Virtual Private Network. Extremely high values often mean a blocked or slow path, not a broken browser.
Does this measure download speed?
No. It focuses on response latency. Throughput (Mbps) needs a dedicated speed test that transfers larger amounts of data.