Website Response Time Test
Measure HTTP response time (not bandwidth) from multiple global locations. Test full request lifecycle from connection to response.
About Latency Test
Test network latency and round-trip time from 6 global probe locations. Measure connection latency, TCP handshake time, and network path efficiency.
Key Features
Multi-region latency testing
Time to First Byte (TTFB)
Connection time measurement
DNS lookup time
Historical comparison
Website response time measures how quickly your server completes an HTTP request—from connection to full response. This is NOT a bandwidth or download speed test; it measures server responsiveness and the complete HTTP transaction lifecycle including DNS, connection, SSL handshake, and data transfer.
Our response time test runs from 6+ global locations, breaking down each component of the HTTP request. You'll see exactly where time is spent: slow DNS resolution, connection delays, SSL overhead, or slow server processing (TTFB). This granular view helps target optimization efforts.
For deeper analysis, use TTFB checker to isolate server-side processing time, or network latency test to measure raw connection latency separate from HTTP overhead. Verify DNS configuration isn't adding unnecessary lookup time.
**Methodology:** Full HTTP request lifecycle measurement from 6 regions: DNS + TCP + SSL + TTFB + transfer, with component-level breakdown.
Common Errors & How to Fix Them
4 relevant issuesThe server responded but took too long. This affects user experience and may indicate server performance issues.
1) Identify bottleneck: check DNS time, connect time, TTFB separately. 2) If DNS slow: switch to faster DNS provider. 3) If TTFB slow: optimize server-side code, add caching, check database queries. 4) If transfer slow: enable compression (gzip), optimize assets. 5) Consider CDN for geographic distribution.
The server didn't respond within the expected time. Could be server overload, network issues, or firewall blocking.
1) Check if server is reachable: ping example.com. 2) Test specific port: nc -vz example.com 443 -w 5. 3) Check from different location (VPN/proxy). 4) For owners: verify firewall allows traffic (ufw status), check server resources, ensure service is running.
The gateway server didn't receive a timely response from the upstream server. The upstream server is too slow or unresponsive.
1) For site owners: increase timeout values (proxy_read_timeout in nginx). 2) Optimize slow backend code/queries. 3) Check database performance. 4) Add caching layers. 5) Test: curl -I -m 30 https://example.com to check response time.
The website is accessible from some locations but not others. This indicates CDN issues, regional server problems, or DNS propagation delays.
1) Check CDN status page (Cloudflare, Fastly, etc.). 2) Verify DNS propagation: dig example.com @8.8.8.8 vs dig example.com @resolver.different-region.com. 3) Check origin server logs for errors. 4) For CDN issues: purge cache, check origin connectivity. 5) May need to wait for DNS propagation.
Frequently Asked Questions
4 relevant questionsLatency is the time delay between sending a request and receiving the first response. High latency makes websites feel slow and unresponsive. For e-commerce sites, every 100ms of latency can reduce conversions by 1%. Latency affects user experience, SEO rankings, and ultimately your bottom line.
For total page load: under 2 seconds is good, under 1 second is excellent. For TTFB specifically: under 200ms is good, under 100ms is excellent. For API endpoints: under 100ms is expected. Mobile users are less tolerant—aim for even faster times. Google considers Core Web Vitals in rankings, making performance crucial for SEO.
Total latency includes: DNS lookup (finding the IP address), TCP connection (establishing connection), SSL/TLS handshake (for HTTPS sites), server processing (generating the response), and data transfer (sending the response). Our latency test breaks down each component so you can identify bottlenecks.
Latency varies by physical distance to the server, network routing efficiency, and CDN coverage. A user in London accessing a server in New York experiences higher latency than someone in Boston. Multi-region latency testing reveals where your performance is weakest and whether your CDN is working effectively.
Related Tools
View All Tools →Related Tools
Global Infrastructure Verification
Verify SSL certificates, DNS records, and connectivity from 6+ regions worldwide. Get automated monitoring, expiry alerts, and full API access.