Response Time Monitoring
Response time (also called latency) is how long it takes a server to respond to a request — the delay between a client asking for a page or resource and the first byte of the reply coming back. A site can be fully available and still feel broken to visitors if its response time is consistently slow, so response time monitoring tracks performance over time, not just whether a site is up or down.
How response time is measured
Response time monitoring works by sending requests to a site at a fixed interval and timing how long each one takes to complete, then tracking that value over time to catch both sudden spikes and gradual degradation. Measuring from a single location only tells you about performance from that one vantage point; measuring from multiple global locations shows whether slowness is a worldwide problem or specific to one region — for example, a site hosted in Europe will naturally show higher latency to a visitor on another continent purely due to network distance, which is a fact of geography, not necessarily a fault to fix.
What "good" response time looks like
There's no single universal threshold, because acceptable response time depends on what the request is doing — a simple static page should return in well under a second, while a complex API call or database query naturally takes longer. What matters more than any absolute number is consistency and trend: a site that suddenly takes three times longer than its normal baseline is showing a real problem, even if the absolute number still looks acceptable in isolation.
Common causes of slow response times
Typical causes include an overloaded or under-resourced server, an inefficient or unindexed database query, a scheduled task like a backup or batch job competing for resources, a slow or misconfigured third-party dependency the page waits on, and simple network distance between the visitor and the server. Some of these — like scheduled maintenance windows — are predictable and can be correlated against a response-time graph after the fact to confirm the cause.
How HostTracker monitors response time
HostTracker measures response time as part of its 14 check types, run from 300+ monitoring locations worldwide, so you can see whether a slowdown is global or regional and whether it correlates with a specific time or event. Run a free check with the page speed test, or set a response-time threshold with continuous distributed monitoring so you're alerted before slowness turns into a full outage. See the page speed guide for more on diagnosing and fixing slow pages.