Website performance and health monitoring: what to measure and when to alert

Response time, percentiles, TTFB and Core Web Vitals: how website performance monitoring works, synthetic vs real-user data, and the health checks that catch problems weeks early.

· 4 min read · By the Spot Downtime team

A site that takes eight seconds to load is up as far as an uptime check is concerned, and losing visitors all the same. Website performance monitoring tracks how fast your pages are over time, so a slowdown gets noticed when it starts, not when customers complain. Website health monitoring adds the slow-moving risks around it: certificates, domains and DNS.

Synthetic vs real-user monitoring

SyntheticReal-user (RUM)
HowA robot loads the page on a scheduleA script on your pages reports what visitors experience
StrengthsConsistent, works with no traffic, catches problems at 3 a.m.Real devices, networks and countries
Blind spotsOne device and network; not your real audienceNeeds traffic; says nothing when nobody visits
Best forAlerting and trendsUnderstanding and prioritising fixes

Uptime monitors are synthetic. They're the right tool for alerting because they run whether or not anyone is visiting. RUM is the right tool for deciding what to optimise.

What to measure

Response time, as percentiles

Averages hide pain. If 19 requests take 100 ms and one takes 3 seconds, the average is 245 ms, a number that describes none of them, while one visitor in twenty waits 3 seconds. Watch the p95 (the time 95% of requests beat) and p99 alongside the median. Spot Downtime records every check's response time and shows p50, p75, p95 and p99 for each monitor.

The average, 245 ms, describes none of the 20 requests. p50 and p95 tell the real story.

Time to first byte

TTFB is how long the server takes to start answering. It's the part you control on the back end: slow database queries, cold caches, an overloaded server. A rising TTFB with an unchanged page is almost always a server-side problem.

Core Web Vitals

Google's three page-experience metrics, measured in a real browser:

  • LCP (Largest Contentful Paint): when the main content appears. Good is 2.5 seconds or less.
  • INP (Interaction to Next Paint): how quickly the page responds to taps and clicks. Good is 200 ms or less.
  • CLS (Cumulative Layout Shift): how much the page jumps around while loading. Good is 0.1 or less.
Each metric has a good, a needs-improvement and a poor band. This sample page is fast to show, slow to respond.

These need a full browser load, so they're measured less often than uptime: on each release, or weekly. The website speed test runs Lighthouse and shows all three with a filmstrip and request waterfall.

Alert on slowness, not just downtime

The useful alert is “slower than normal for a while”, not “one slow request”. On Starter and Pro, a Spot Downtime slowness alert fires when a monitor's p95 response time stays above a threshold you set, without counting it as downtime. Set the threshold a little above your normal p95, so it fires on a real change rather than every busy hour. The response time guide shows how to pick it.

Website health monitoring

Performance is one part of a site's health. The rest are checks that catch problems days or weeks before they become outages:

CheckCatchesIn Spot Downtime
SSL certificate expiryA renewal that silently failedWarnings 14, 7 and 1 day before
Domain expiryA lapsed card on the registrar accountWarnings 30, 7 and 1 day before
DNS recordsA record changed or deleted by mistakeDNS monitors
Keyword on the pageA 200 that serves an error pagePage must contain
Background jobsBackups and queues that stoppedHeartbeats
Broken linksPages and assets that 404Broken link checker

What we don't do

Spot Downtime doesn't collect real-user data: there's no script to add to your pages. If you need RUM, use it alongside an uptime monitor rather than instead of one. RUM can't alert you when nobody can reach the site, because then there are no visitors to report anything.
Website speed testLighthouse score, Core Web Vitals, DNS, TLS and TTFB timings for any page, free.

Get new guides by email

Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.

Unsubscribe from any email with one click. See our privacy policy.

Keep reading