Uptime and heartbeats
Know whether the release held with availability checks.
Ingest Lighthouse runs from CI or local, grade them against per-metric budgets, and keep the score, the metrics, and the artifact beside the commit that produced them.
92
Perf
One connected loop, held on the stage this capability serves. The other stages stay as context so you can see what feeds in and what comes next.
Know whether it held.
Know whether the release held with availability checks.
Keep incident response and customer-facing status context together.
Review Lighthouse report evidence against configured targets.
Investigate test outcomes and flakiness evidence across runs.
Each core web vital fills to how much of its budget it spends. A metric over budget flags red and pulses; the passing ones settle and stay still.
1.8s/ 2.5s
largest contentful paint
0.02/ 0.10
cumulative layout shift
240ms/ 200ms
interaction to next paint
120ms/ 200ms
total blocking time
Requests reveal staggered left to right in load order, the same way a network panel draws them, so a render-blocking script is easy to spot.
resource waterfall · load order
Every run records accessibility, best practices, SEO, and PWA alongside performance, each scored 0 to 100.
Set a threshold per metric with a comparison operator and a severity. Each run rolls up to one pass, warn, or fail verdict.
88
Perf
An honest limit
Web performance is Lighthouse-based. It ingests lab runs pushed from CI or local, not real-user monitoring, full APM, or distributed tracing, and it does not crawl your URLs on its own.
Ingest a report and start tracking.