Why your Lighthouse score isn't the SEO win you think it is

Every agency loves a Lighthouse screenshot. Four green circles, 100/100 across the board, the kind of result that looks like proof. We use them too — they’re on our case study pages and they’re a real signal of a well-built site.

But Lighthouse is a tool, not a strategy. And quite a lot of bad sites have 100/100 scores. Here’s how.

What Lighthouse actually measures

Lighthouse, the auditing tool inside Chrome DevTools, scores a page across four categories: Performance, Accessibility, Best Practices, and SEO. Each is a composite of a few dozen automated checks.

Crucially, Lighthouse is a lab tool. It loads your page in a simulated environment, with a simulated connection, and grades what it sees. It does not measure what real users experience. It does not check whether your site actually ranks. It does not know whether your content is any good.

The four ways a “100/100” site can still be broken

1. It’s a thin page. Lighthouse scores well on speed because there’s almost nothing to load. We’ve audited sites with perfect Lighthouse scores and 80 words on the homepage. Lighthouse loved them. Google didn’t.

2. The schema is empty. Lighthouse’s SEO score checks that you have schema, not that the schema is correct or useful. We’ve seen sites passing Lighthouse SEO with LocalBusiness markup pointing at an address that didn’t match the business.

3. The Accessibility score is automated-only. Lighthouse can spot a missing alt text or a low-contrast colour pair. It cannot tell you whether a screen reader can actually navigate the site, whether keyboard focus is sensible, or whether your forms are usable for someone with limited dexterity. Those things matter and Lighthouse doesn’t measure them.

4. The Best Practices score is too forgiving. “Uses HTTPS” and “no console errors” will tick Best Practices boxes. They don’t tell you whether the underlying architecture is sound, whether your dependencies are up to date, whether you’re leaking data, or whether the site will still be maintainable in eighteen months.

The metric that actually predicts rankings

If you want one performance metric that genuinely correlates with how Google treats your site, it’s Core Web Vitals — measured on real users, not in a lab. Specifically:

• LCP (Largest Contentful Paint) — how fast the biggest above-the-fold element appears. Target: under 2.5 seconds on the 75th-percentile mobile visitor.
• INP (Interaction to Next Paint) — how quickly the page responds when a user taps. Target: under 200 milliseconds.
• CLS (Cumulative Layout Shift) — how much the layout jumps around as it loads. Target: under 0.1.

These are measured in Google’s Chrome User Experience Report (CrUX), aggregated from real Chrome users browsing real sites. They directly feed into Google’s ranking signals. Lighthouse approximates them in the lab, but the real numbers are what matter.

So what should you actually look at?

Three things.

First, the Search Console “Core Web Vitals” report. Real-world data, segmented by URL group, updated daily. If this says your site is failing LCP on mobile for 40% of visits, that’s what’s worth fixing — not whatever Lighthouse said this morning.

Second, the “Page Experience” report in Search Console, which combines Core Web Vitals with HTTPS, mobile-friendliness, and a handful of other practical signals.

Third, your actual rankings, tracked over time for the queries that matter to your business. A site that’s slowly climbing for high-intent local queries is winning, even if its Lighthouse score has wobbled. A site stuck at 100/100 Lighthouse and page-five rankings is still losing.

What we do at Copper Lane

We do tune for Lighthouse — but as a side effect, not the goal. The actual goal on every build is:

• LCP under 1 second on mobile, on the 75th-percentile visitor
• INP comfortably under 100ms
• CLS at or near zero
• Real-world Core Web Vitals passing in Search Console within a month of launch

Hit all those and Lighthouse will give you a great screenshot for free. Optimise for the screenshot and you’ll get a screenshot and not much else.