Skip to main content
A11y Pulse vs Google Lighthouse

A Lighthouse score is a snapshot.
A11y Pulse is the time-lapse.

Lighthouse gives you a single accessibility score for a single page, on demand. A11y Pulse scores every page on your site, every day, and tells you the moment that score slips.

What is Lighthouse?

Lighthouse is Google's open-source auditing tool. It's built into Chrome DevTools and PageSpeed Insights, and runs a curated bundle of axe-core rules to produce a 0–100 accessibility score. The score sits alongside Performance, Best Practices, and SEO in the same report.

Chrome DevTools Built into the browser

Right-click → Inspect → Lighthouse. Free, on whatever page you currently have open.

PageSpeed Insights pagespeed.web.dev

Public URL form. Runs the same audit, no install needed.

Lighthouse CI GitHub Action or CLI

Open-source. Schedule per-PR runs and store the JSON yourself. Dashboards are DIY.

Why teams switch to A11y Pulse

Three things a Lighthouse score won't tell you

Lighthouse is excellent for one URL on demand. Production accessibility needs the things it isn't trying to be.

1

Coverage

Whole site, not one page

Lighthouse audits the page in front of you. A11y Pulse audits every page on your sitemap, so issues isolated to checkout, search results, or article templates surface without anyone remembering to check.

Every page, every day

2

Continuity

Yesterday vs today, automatically

A score with no history can't answer "did this CMS edit make it worse?" A11y Pulse keeps a 30-day trend per page and alerts you within hours when something regresses.

Regression alerts in 24h

3

Triage

Tickets, not just numbers

An 88 is interesting; "three new contrast failures on the checkout template" is actionable. A11y Pulse groups issues by template and rule so a single fix clears every instance.

Grouped by template

Where we fit

The dashboard Lighthouse never shipped

Lighthouse gives you a score and a JSON file. A11y Pulse turns the same axe-core findings into a continuous, filterable workspace your team actually opens on Monday morning, with scheduling, history, and alerts your CI pipeline isn't designed to provide.

  • axe-core daily across your full sitemap, in real Chromium
  • Issues grouped by template so one fix clears every page
  • Score trend per page, kept for the life of your account
  • Regression alerts via email, Slack, or Microsoft Teams
The A11y Pulse dashboard showing a 30-day scan history chart, the issue count, and a list of pages with their current accessibility scores.

Side by side

A11y Pulse vs Lighthouse

Pricing
Testing engine
Scope
Scheduling
Page discovery
History and trends
Regression alerts
Authenticated pages
Stakeholder reporting
Best for
A11y Pulse Continuous, site-wide
Recommended
$19 USD/month Hosted, monthly billing
axe-core
Whole site, daily Up to 1,000 pages
Daily, with unlimited rescans
Sitemap, crawl, or URL list
30-day deltas + monthly reports
Email, Slack, Microsoft Teams
Scripted login flow
Monthly email with delta vs prior month
Continuous monitoring across whole sites
Lighthouse DevTools audit score
For comparison
Free Open source
axe-core With Google scoring weights
One page, on demand
None Manual runs
Single URL only
None Save the JSON yourself
Not included
Manual via DevTools or custom Puppeteer
Not included
Developer spot checks during a build

Lighthouse data reflects the version shipped with Chrome and the Lighthouse Node CLI as of May 2026. Lighthouse CI is a separate Google project for running Lighthouse inside a build pipeline.

A note on the score

Two scoring algorithms, two different stories

Both tools produce a 0–100 score, and the numbers can disagree. The Lighthouse score is a weighted average of binary pass/fail audits. A single button without an accessible name fails the "Buttons have an accessible name" audit outright regardless of how many other buttons pass, and that failure is weighted against the other audits. The result is sensitive to which axe-core rules a page hits but relatively insensitive to how many violations of each rule live on the page.

The A11y Pulse score takes a different shape. Every page starts at 100, and every violation deducts points by severity: 20 for a Critical, 15 for a Serious, 5 for a Moderate, 2 for a Minor. The page score floors at 0; the site score averages across all tracked pages. A page with thirty colour-contrast failures scores visibly lower than a page with one. Scores fall into Good (90–100), Needs Improvement (70–89), and Poor (0–69) bands.

Neither algorithm is "correct". Lighthouse's weighting reflects axe-core's per-audit user-impact assessment. A11y Pulse's deduction model reflects the actual count of violations a developer will work through. For a stakeholder slide, the A11y Pulse score plus the monthly delta is the version that holds up best, because it answers both "where are we" and "are we improving".

The verdict

When each tool is the right call

Choose

A11y Pulse

  • You're shipping to production and need to keep accessibility scores up
  • You want regression alerts before users notice
  • You're managing accessibility across more than one or two pages
  • You want a site-wide score plus per-page scores, with history
  • You need pages behind a login tested without writing a Puppeteer script
  • You want a stakeholder report that shows the trend, not just the headline

Choose

Lighthouse

  • You're a developer doing a quick check on a page you have open
  • You want a free tool that runs locally inside Chrome DevTools
  • Your priority is the broader Lighthouse score across performance, SEO, and accessibility together
  • You want a CI gate via Lighthouse CI that fails a build on a score regression
  • You only have one or two pages to keep an eye on

Common questions

You asked.
We answered.

Still curious? Read the docs or email us.

Yes. Lighthouse's accessibility category is a thin wrapper around axe-core, with Google's own scoring weights applied on top. A11y Pulse runs axe-core directly. The underlying issue list for a given page should be substantially the same in both tools; the difference is everything around the engine, including scheduling, history, multi-page coverage, alerting, and reporting.

The information presented here about A11y Pulse and Lighthouse is provided for comparison purposes and may change over time. Pricing and feature claims about Lighthouse should be verified on their own website before making a purchasing decision.

From one score to one watching brief

Connect your site and we'll score every page nightly. 14-day free trial, no credit card.

Start your free trial