What Is a Good Server Response Time? Benchmarks That Matter

"Fast enough" is a moving target, but the numbers are well understood. Here's what a good server response time looks like, what drags it down, and how to catch regressions early.

Response time vs. TTFB vs. page load

These get mixed up constantly:

• Time to First Byte (TTFB) — how long from request until the first byte of the response arrives. It mostly reflects your server and network.
• Server response time — how long the server takes to generate and return the response.
• Full page load — everything, including images, scripts, and fonts in the browser.

Uptime monitors typically measure the first two, which are the parts your backend controls.

Benchmarks

As a rough guide for server response / TTFB:

• Under 200 ms — excellent. Feels instant.
• 200–500 ms — good. Fine for most sites.
• 500 ms – 1 s — acceptable but worth improving.
• Over 1 second — users notice. Investigate.

Google has long suggested keeping server response time under 200 ms. Real numbers depend on geography and what the request does, but if a simple page consistently takes more than a second on your server, something is wrong.

What slows a server down

The usual suspects, roughly in order:

1. Slow database queries — missing indexes, N+1 queries, table scans.
2. No caching — regenerating identical pages on every request.
3. External calls — a slow third-party API blocking your response.
4. Under-provisioned hosting — CPU or memory contention under load.
5. Cold starts and far-away servers — physical distance adds latency.

Watch for regressions, not just outages

A site can be "up" the whole time and still get slowly, steadily worse after a deploy or as data grows. That's why response time matters as much as up/down. A good practice is to alert on degradation — when response time is sustained at, say, 2× its normal baseline — so you catch the slow creep before it becomes a customer complaint.

How to track it

Record response time on every check and look at the trend over weeks, not minutes. SiteIsOnline stores response time per check and per day, shows the trend on your dashboard, and can alert you when a monitor gets sustainedly slower than its 7-day baseline.

[Start monitoring your response times free](/register) — and if you just want a one-off reading, the [free site checker](/tools/website-down-checker) reports response time instantly.