Lighthouse Audit

Run a live Lighthouse audit against any URL and enforce score thresholds as quality gates.

▶How this works

Mechanism

Jerry launches a headless Chromium browser with --remote-debugging-port so Chrome exposes its native CDP HTTP server. The Lighthouse npm package connects to that port and runs a full audit — the same engine used in Chrome DevTools. Results are checked against your threshold sliders.

Quality gates

Each score category (Performance, Accessibility, Best Practices, SEO) is compared against its threshold. If any score falls below its threshold, the overall audit is marked as failed. Results are persisted to Supabase and appear in the history panel.

Why this matters for QE: Lighthouse scores are objective, reproducible performance and accessibility metrics. Gating deploys on them means accessibility regressions and performance degradations are caught in CI, not in production.

audit_config

Target URL

Score Thresholds

Performance80

Accessibility90

Best Practices85

SEO80

audit_results

Enter a URL and run an audit to see results