Your Lighthouse scores, tracked over time.
Run real Lighthouse audits on a schedule, keep every score in history, and get an incident when performance drops 15 points.
You ran Lighthouse at launch. Then the site kept changing.
Scores decay the same way sites do: a marketing script here, an oversized hero image there, a dependency bump that ships more JavaScript. Nobody notices, because nobody reruns the audit.
UptimeStatus runs Lighthouse against your monitor's URL on a schedule and records all four category scores every time: performance, accessibility, SEO, and best practices. The audit that used to be a launch-week ritual becomes a data series you can actually watch.
A 15-point performance drop opens an incident.
Every new audit is compared against the previous one. If the performance score falls by 15 points or more, UptimeStatus opens an incident with both numbers in it and notifies your channels, the same pipeline your uptime alerts use.
That means the deploy that doubled your bundle size shows up as an event on a timeline, not as a mystery in next quarter's Core Web Vitals report.
What Lighthouse monitoring includes.
- Four categories tracked performance, accessibility, SEO, and best practices, each scored 0 to 100 like the Lighthouse you already know.
- Real headless Chrome the actual Lighthouse tool runs against your URL. Same methodology, same numbers as DevTools.
- Score history per monitor every audit is stored, so you see trends across deploys instead of one-off snapshots.
- Performance regression incidents a performance score that drops 15 points or more against the previous audit opens an incident.
- Full report kept the complete Lighthouse JSON is stored with every audit, so you can drill into exactly which audits failed.
- API access list and inspect reports at /api/lighthouse-reports and build whatever dashboard you want on top.
The same audit you would run by hand.
No proprietary scoring model to second-guess. The worker runs the real Lighthouse tool in headless Chrome, and the open-source code shows exactly how. Self-host it anywhere; the only extra requirement for this check type is Chrome or Chromium on the worker host.
Reports are data, not screenshots.
Every audit is stored as a record: four scores, a timestamp, and the full Lighthouse JSON for drill-down. Pull them over the API to chart score history in your own tools, gate a release on the latest numbers, or archive reports somewhere else.
If it is in the dashboard, it is in the API.
# list Lighthouse reports for your monitors curl https://uptime-status.org/api/lighthouse-reports \ -H 'Accept: application/json' # fetch one report, full JSON included curl https://uptime-status.org/api/lighthouse-reports/142
Lighthouse monitoring, answered.
Is this real Lighthouse or an approximation?
Real Lighthouse, running in headless Chrome on the worker. The scores match what you would get from Chrome DevTools or the Lighthouse CLI, because it is the same tool.
Do I get alerted when a score drops?
Performance drops do alert: if the performance score falls 15 points or more compared to the previous audit, an incident opens and routes through your notification channels. Accessibility, SEO, and best-practices scores are tracked with full history so you can watch their trends, but they do not open incidents on their own.
Can I see why a score dropped?
Yes. The full Lighthouse JSON report is stored with every audit, so the failed audits and opportunity details behind each score are there when you need them, not just the four headline numbers.
What do I need to self-host this check?
Chrome or Chromium installed on the worker host. Lighthouse needs a real browser, and this is the one check type that does. If Chrome is missing, the job logs a clear warning instead of failing silently.
Will audits slow down my other checks?
No. A Lighthouse audit takes seconds rather than milliseconds, so it runs on its own dedicated queue and does not share a worker pool with your uptime, ping, or TCP checks.
Pairs well with.
Performance monitoring
Lighthouse audits your page loads. p95 baseline comparison watches your response times between audits.
Learn moreBroken links
A daily crawl for 404s, mixed content, and dead sitemap URLs. The other kind of quiet decay.
Learn moreUptime monitoring
30-second checks from six regions, with full diagnostics on every result.
Learn moreStart monitoring in under 2 minutes.
No credit card required for the self-hosted, open-source version.