What is a good website response time?
Response time is how long a website takes to start answering after you ask for a page. It is measured in milliseconds, where 1,000 ms is one second. It is not the same as total page load time, which also includes images, scripts and rendering.
Rough guide
- Under 200 ms: very fast. The server answers almost at once.
- 200 to 500 ms: good for most sites.
- 500 ms to 1 second: acceptable, but noticeable on a slow connection.
- Over 1 second: slow. Visitors begin to notice, and some leave.
These figures are rules of thumb. A very busy checkout page or a search engine has different needs from a simple blog.
Why the number changes
- Distance. A visitor on the other side of the world takes longer to reach a single server than one nearby. That is why we show response times from several regions.
- Server load. A busy server answers more slowly.
- Page generation. Sites that build each page from a database take longer than sites that serve saved pages.
- Connection setup. Finding the server, connecting and securing the link all add time before any content arrives.
- Your own connection. Weak Wi-Fi and mobile signal add delay that has nothing to do with the site.
How to improve it
Use caching, a CDN, compressed responses and a fast host. The speed-up guide goes through the changes that make the biggest difference.
How we measure it
Our live graph shows the response time of our own checks, which include network travel. A single slow reading is normal. Look at the average over a day or a week.
Is it down for everyone, or just you? Paste an address and we test it from fifteen places.
Open the checkerRelated guides
- How to speed up your website: the checks that matter most
- Uptime percentages explained: what 99.9% really means
- How siteupdown.com checks a website, and what the verdicts mean
Last updated 2 November 2026. Written by the siteupdown.com team. Spotted a mistake?