Online latency checker
Check whether a site responds from the browser before you dig through DNS, SSL, CDN, or app code.
Note: This tool measures HTTP reachability with the Fetch API, not a real ICMP ping. The timing includes DNS, TCP, TLS, and server response time, which makes it a practical browser-side approximation of how a visitor experiences your site.
Recent checks
Latency basics
Low latency
Under 100 ms: great for interactive apps, live previews, and calls.
100-200 ms: usually still smooth for everyday browsing.
High latency
Over 300 ms: users begin to feel noticeable lag.
Over 500 ms: pages often feel slow and need investigation.
What this check includes
Browser timing can include DNS, TCP, TLS, redirects, cache behavior, and server response time.
Use it as a visitor-style reachability check, then inspect CDN, origin, and backend traces when the number looks wrong.
Frequently asked questions
Why is the latency higher than I expected?
Latency rises when the server is far away, the network is congested, the connection is unstable, or the origin itself is slow. The browser measurement also includes connection setup and server processing time.
What is TTFB?
Time to First Byte measures how long it takes for the browser to receive the first byte of the response. It is a useful signal for network path, CDN behavior, origin processing, and backend responsiveness.
Why is this different from terminal ping?
Terminal ping usually uses ICMP. Browser checks use HTTP requests, so they better approximate whether a web page can be reached but include more moving parts.
Why can one region be fast while another is slow?
Distance, peering, CDN routing, cache hit ratio, origin location, and local network quality all affect latency. Global sites should be checked from more than one network path.