What this response time checker measures
We start a clock, send a GET, follow up to five redirects, and stop when the response is in. The timeout is 10 seconds. You get one sample from our server, not a browser time-to-first-byte, not Largest Contentful Paint, and not a median. We do not download images or run JavaScript, so a site can be fast here and slow on a phone.
The label beside the number is only a reading aid. Under 300 ms is quick for this kind of request. From 300 ms to 800 ms is ordinary once distance and a redirect are included. Over 800 ms is slow for a single GET, and over 2 seconds is worth a look. None of those bands is a Core Web Vitals threshold or a pass/fail grade.
How to read a single sample
The number answers one question: how long did our server wait for this URL just now? Run it twice. If the two results are far apart, you are seeing jitter or a cold cache, not a stable average. If both are slow, the slowness is real for this path at this time.
Redirects are inside the number. A URL that hops across two hosts will look slower than the final host alone. Check the final URL directly if you want to separate that tax from the page. A timeout is an error with no response time, not a successful 10000 ms. The site did not answer.
Common reasons a check is slow
Slow means our request waited. The fix depends on which part of the wait grew.
- A long redirect chain, or a redirect to a distant host. Collapse it.
- A cold DNS lookup or a long path from our server. Repeat the check before you redesign anything.
- Heavy work on the request: a slow query or a remote API call. The status can still be 200.
- The host is overloaded. Response time usually climbs before 502s and 503s start.
- A firewall tarpitting datacenter traffic. Your laptop looks fast; this checker looks slow or blocked.
One sample will not tell you tomorrow
A fast result this morning says nothing about the deploy at 4 p.m. A monitor repeats the check and stores the latest response time: every 10 minutes on the free plan (5 monitors), every 5 minutes on Pro, and every minute on Business. Alerts fire when the URL is down, on WhatsApp, Telegram, Slack, or email. A slow 200 is still up.