Monitoring
Lighthouse Monitoring
Scheduled Lighthouse audits — Performance, Accessibility, Best Practices and SEO scores tracked over time, with an alert when a score drops below your minimum.
A Lighthouse monitor runs a real Lighthouse audit against your page on a schedule and records its four category scores — Performance, Accessibility, Best Practices and SEO (0-100) — plus its lab metrics (LCP, CLS, FCP, TBT, Speed Index, server response time), so a regression shows up as a trend instead of a surprise.
Availability
Requires a plan with Lighthouse Monitoring (Professional and above).
How it works
curl -X POST https://api.monsphere.com/api/v1/organizations/{orgId}/monitors \
-H "X-Api-Key: msph_live_..." -H "Content-Type: application/json" \
-d '{
"name": "Homepage Lighthouse",
"type": "lighthouse",
"target": "https://example.com",
"intervalSeconds": 21600,
"config": {
"lighthouseFormFactor": "mobile",
"lighthouseMinPerformanceScore": 70,
"lighthouseMinSeoScore": 90
}
}'- The monitor goes down when Lighthouse can't audit the page or a category scores below its minimum — e.g.
Performance score 42 below 70. lighthouseMinPerformanceScore,lighthouseMinAccessibilityScore,lighthouseMinBestPracticesScore,lighthouseMinSeoScore— optional, 0-100. Left out, each defaults to 50 (Lighthouse's own red/orange boundary); a negative value means "track this score, never alert on it".lighthouseFormFactor—mobile(default, the profile Google ranking uses) ordesktop.- One audit takes roughly 15-60 seconds, so Lighthouse runs at most every 30 minutes and a failed audit is not retried until the next scheduled run.
How it runs
Audits run on their own dedicated queue and worker, isolated from every other monitor's checks, in a sandboxed headless Chromium with the same network guard every browser-based check uses. There's no region to pick — audits run from the central worker.
Bot protection and error pages: if the site serves a bot-protection challenge (such as Cloudflare's "Just a moment...") or the page returns an HTTP error status, the page isn't audited — the monitor goes down and says why, instead of recording results for the challenge or error page. Allowlist MonSPHERE's checks in your bot protection, or monitor a page that isn't behind it.