Measure
Every check, timed
Each uptime check records response time. On paid plans with 1-minute (or 30-second) intervals, you get a high-resolution picture, not hourly samples.
Response time
Slow is the warning.
Down is the outage.
Most outages announce themselves first as a slowdown. UptimeClaw tracks response time on every check, keeps 90 days of history, and alerts you on degradation — so you act on the trend, not the incident.
Why it matters
A 200 OK that takes 8 seconds is still a failure.
Uptime checks that only watch status codes miss the most common real-world degradation: the site is technically "up" but crawling. Users bounce, checkout abandons, and Core Web Vitals slide — all while a status-only monitor stays green. By the time it finally times out and flips to "down," you've already lost the traffic.
Tracking response time turns that blind spot into an early-warning system. A steady climb from 300 ms to 2 s over a week is a database, cache, or capacity problem you can fix on your schedule — before it becomes a 3 a.m. page.
How response-time monitoring works
It runs on the checks you already have — no extra agent, no code on your server.
Trend
90 days of history
See the curve, not just the moment. Spot gradual degradation, deploy regressions, and weekly load patterns over a 90-day window.
Alert
Custom thresholds
Set the line that matters for each monitor — alert when response time crosses it, on WhatsApp, email, Slack, or webhook.
Response-time FAQ
Is this the same as page-speed / Core Web Vitals?
It's complementary. Response time measures how fast your server answers a request (TTFB-style), checked continuously from the outside. Lab page-speed tools measure full render once. Continuous response-time tracking is what catches a live slowdown as it happens.
How much history do I get?
90 days, so you can see trends and compare against past performance — not just the latest reading.
Can I alert before the site is fully down?
Yes — that's the point. Set a response-time threshold and get alerted on degradation while the site is still returning 200, giving you lead time to fix the cause.
See the slowdown
before your users do.
Response time on every check, 90-day history. Free to start.
Related guides
Multi-region monitoring · SSL monitoring · All monitoring features