Website Latency Test

Measure how quickly a website responds from outside your own network. We break it down into DNS, time-to-first-byte and total load time.

Reading the numbers

DNS is the time to look up the address, TTFB is how long until the server sends its first byte, and Total is the full response. A high TTFB usually points at the server or database; a high DNS time points at the domain’s nameservers. Multi-region comparison — the same site timed from several places at once — is rolling out.

Watching your own site’s speed over time? Turn on monitoring and PingStuff tracks response time on a schedule and alerts you when a site goes down.

Questions

What is TTFB?
Time to First Byte — how long from the request until the first byte of the response arrives. It captures DNS, connection, TLS and the server’s own “thinking” time, so it’s the single best number for “how snappy does this site feel”.
Why does latency differ by region?
Physical distance adds round-trip time, and a site served from one region (or a CDN with uneven coverage) will answer faster to nearby visitors. Comparing regions shows whether slowness is global or specific to where your users are.
Is this the same as a full health check?
No — this focuses on speed. For a full plain-English health report (DNS, SSL, HTTP status and a score), use the website checker on the home page.
What counts as good latency?
It depends on what the site does. For a content or marketing site, a TTFB under roughly 200 ms feels instant and under 500 ms is fine; interactive apps benefit from staying at the low end. Distance matters too — a region far from your server will always read higher, and that is normal.
Is latency the same as bandwidth?
No. Latency is how long each round trip takes; bandwidth is how much data can flow per second. A connection can have huge bandwidth and still feel sluggish when latency is high, because a page load involves many round trips before the content even starts arriving.

Related tools