Lighthouse Score History: Why Spot Checks Fail You
A Lighthouse score is a snapshot. It tells you where the site stands right now, at this moment, on this run. It doesn’t tell you whether that number has been climbing, dropping, or quietly deteriorating for the past three months while nobody was watching.
Most performance conversations start when a score is already bad. “Why is it 58?” is a harder question to answer than “when did it drop from 91 to 58, and what changed that week?” When a client emails asking why their traffic dropped, an agency without history has to guess. An agency with history can say: your marketing team installed a chat widget on Tuesday.
What Lighthouse actually measures
Lighthouse audits a page across four categories: Performance, Accessibility, Best Practices, and SEO. Each produces a score from 0 to 100, weighted by a set of underlying metrics.
The Performance score gets the most attention, and for good reason. It’s driven by metrics like Largest Contentful Paint, Total Blocking Time, and Cumulative Layout Shift — the same metrics tracked by Core Web Vitals, though with an important distinction: Lighthouse uses lab data (simulated on a throttled device), while Google’s rankings draw on field data gathered from real Chrome users over a rolling 28-day period. Think of Lighthouse as an early warning system for your field data, not a direct proxy for it.
Lab scores also fluctuate. A 3-point variance between runs is normal, Lighthouse is sensitive to server response times and simulated network conditions. A consistent downward slope over multiple runs is a deployment or dependency issue. A score that drops by 15 points over six weeks is almost certainly a real change.
The distinction matters. Reacting to noise wastes developer hours. Missing a real trend costs rankings and client trust.
What changes scores without anyone noticing
Performance scores move whenever the site changes, but not always in ways that are easy to trace.
Third-party scripts are the most common cause of unexplained drops. A marketing team adds an analytics tag, a chat widget gets updated by a vendor, a social sharing plugin loads a heavier version of itself. Each adds to Total Blocking Time. None sends an alert.
Plugin and theme updates on CMS-based sites regularly affect performance. A WordPress update can swap out an image optimisation library, change how scripts are loaded, or alter the render path for above-the-fold content.
Content changes shift scores too. A new hero image that wasn’t compressed correctly, a page template that added a font, an embedded video that loads eagerly instead of lazily. These feel like content decisions, not performance decisions — which is why they go unnoticed.
Lighthouse version updates periodically change how metrics are weighted. A version bump can move scores across the board without a single line of code changing on the site. The Lighthouse release notes track these changes.
Without a history, any of these could explain a drop and there’s no way to narrow it down.
What useful trend monitoring looks like
The goal isn’t a perfect score. It’s a stable score with enough history to catch a change when it happens.
A few things that matter more than most people account for:
All four categories, not just Performance. An Accessibility score that drops after a theme update is worth knowing about. An SEO score that dips after a migration can affect rankings before anyone notices in Search Console.
Enough frequency to catch changes early. Weekly checks give you a seven-day window to identify what changed. Monthly checks can mean a problem runs for weeks before it surfaces.
Per-page tracking, not just the homepage. Lighthouse scores vary significantly between pages. A product page with a heavy image carousel behaves differently from the homepage. Tracking only one gives an incomplete picture.
The pattern that catches problems earliest is a stable baseline, regular checks, and an alert when something moves outside the expected range.
A quick checklist
Before your next performance conversation, check:
- What is the current Lighthouse Performance score for the homepage? For the top three landing pages?
- What was it three months ago?
- Has the Accessibility score changed since the last deploy?
- Are there any third-party scripts on pages that weren’t there six months ago?
- When did Lighthouse last update its scoring weights?
If you can’t answer the second question, you’re working from a snapshot, not a trend.
If you manage sites for clients, answering “what changed?” shouldn’t require a forensic investigation. kant.au automatically tracks Lighthouse score history across all your domains, page by page. Start a free 14-day trial and build your baseline before a client asks for it.