Website Response Time Checker

What this website response time checker measures

When you run a test, our server requests your page three times, each time on a fresh connection, just like a first-time visitor's browser. For every request we record how long each step takes and then show the median, which is less affected by one unusually slow or fast measurement.

• DNS lookup: how long it takes to translate your domain into an IP address.
• TCP connection: how long it takes to open a connection to your server. This mostly reflects network distance.
• SSL/TLS handshake: how long it takes to set up encryption for HTTPS.
• Server processing: the time between sending the request and receiving the first byte of the answer. It includes the work your application does to build the page.
• Time to first byte (TTFB): the sum of all of the above for the final request: the moment the browser can start receiving your page.

Swipe sideways to see the whole diagram

What is a good website response time?

Google's guidance for time to first byte suggests that most sites should aim for 0.8 seconds or less, and treats values above 1.8 seconds as poor. Those thresholds are meant for real users on real networks, so treat our single-location measurement as a useful indicator rather than an exact score. More important than any absolute number is your own baseline: if your site normally answers in 250 ms and suddenly takes 1,500 ms, something has changed.

How to use the breakdown

The phase that takes the longest tells you where to start:

• Slow server processing points to the application: missing page caching, slow database queries, heavy plugins or an overloaded server.
• Slow connection and TLS point to distance and network: a CDN or a hosting region closer to your visitors helps, as does TLS 1.3.
• Slow DNS points to the DNS provider or long chains of CNAME records. Check your records with the DNS lookup tool.
• A big gap between TTFB and total means redirects. Inspect them with the HTTP status checker.

For a complete explanation of each factor and how to improve it, read our guide to website response time.

Track response time continuously

A single test is a snapshot. Response time changes during the day and drifts over weeks as databases grow and traffic changes. UptimeStats records the response time of your website on every check, every 5 minutes, and shows 24-hour and 7-day charts, so you can spot slowdowns early and get an alert if your website stops responding. Learn more about uptime monitoring.