See how fast your website loads in each region
Enter a target to test from multiple regions
Global latency distribution
| Region / ISP | Fastest | Slowest | Average |
|---|---|---|---|
DNS resolution statistics
Understanding HTTP timings
Compare DNS resolution, TCP connection, TLS negotiation, time to first byte and download duration across probe locations to find the slow stage.
A website speed test sends a real HTTP or HTTPS request from each node and splits the time into DNS lookup, TCP connect, TLS handshake, time to first byte (TTFB) and download. The slowest stage usually points straight at the cause: slow DNS suggests the DNS provider or recursive path, slow TCP suggests distance or route quality, slow TLS suggests a long certificate chain or a busy server, and a slow TTFB means the application itself is slow.
If you use a CDN, the test also shows whether routing works: each region should be served by a nearby edge IP.
Frequently asked questions
What can increase time to first byte?
Server processing, a cache miss or the network path to the origin can all increase it. Compare the other timing stages and repeat the test.
What is a good TTFB?
Within the same region, aim for under 200 ms; across countries, under 500 ms is acceptable. If every region is slow, optimize the backend or database. If only distant regions are slow, the issue is the network or missing CDN coverage.
Is a 301 or 302 response a problem?
Not necessarily. Redirecting HTTP to HTTPS or the bare domain to www is normal, but every redirect adds a full round trip, which is expensive across borders. Avoid chains of several redirects.
Ping is fast but the website is slow. Which result is right?
Trust the website speed test. Ping only measures network round trips, while users experience the whole HTTP request, including DNS, TLS and server processing. Fast ping with a slow site means the bottleneck is in the application, not the network.