Do Core Web Vitals Still Matter for Rankings in 2026?
By Paul Lovell · March 12, 2026 · 4 min read
Core Web Vitals dominated SEO conversations when they launched, then largely faded from industry attention once it became clear they weren't the dramatic ranking lever many expected. That's led plenty of site owners to deprioritise page experience work entirely. That's a mistake — just not for the reason most people assume.
The three metrics and their thresholds
Worth restating, because a surprising number of teams are still optimising against the pre-2024 set:
| Metric | Measures | "Good" threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | Loading — when the main content appears | Under 2.5 seconds |
| Interaction to Next Paint (INP) | Responsiveness — delay between interaction and visual response | Under 200 milliseconds |
| Cumulative Layout Shift (CLS) | Visual stability — unexpected movement of page elements | Under 0.1 |
INP replaced First Input Delay on March 12, 2024. If your monitoring or reporting still references FID, it's measuring a metric Google retired two years ago. That's the most common stale-configuration problem I still see.
The distinction matters because FID only measured the delay before the browser began processing the first interaction — a famously forgiving metric that most sites passed trivially. INP measures the full duration until the next visual update, across all interactions on the page. Sites that comfortably passed FID routinely fail INP, and the reason is usually heavy JavaScript execution blocking the main thread on interaction.
The direct ranking impact was always modest
Google has been consistent that Core Web Vitals are a comparatively small ranking signal, mainly acting as a tiebreaker between pages that are otherwise similarly relevant. If your content isn't competitive on relevance and quality, no amount of LCP optimisation will fix that. This is well understood and isn't really up for debate.
You'll find articles assigning Core Web Vitals a specific percentage weight in Google's ranking systems. Treat those with scepticism — Google has never published such a figure, and any number of that kind is inference presented as fact.
The indirect impact is where it actually matters
Where Core Web Vitals still earn their keep is in user behaviour, not raw rankings:
- Bounce rate and engagement. Slow or janky pages lose visitors before they engage with content.
- Conversion rate. For commercial sites, page speed has a well-documented, direct relationship with conversion that has nothing to do with search rankings at all. This is usually the argument that actually gets the work funded.
- Crawl efficiency. Faster pages are cheaper for Googlebot to crawl, which matters more for large sites competing for crawl budget than for smaller ones.
Field data beats lab data
One methodological point that trips up a lot of teams: Lighthouse scores are lab data, simulated on a synthetic device and connection. Google's ranking systems use field data — the Chrome User Experience Report, collected from real Chrome users on real devices and networks.
A perfect Lighthouse score with failing CrUX data is common, particularly on sites whose real users are on mid-range Android devices while the audit runs on a simulated fast connection. Check the Core Web Vitals report in Search Console, which uses field data, before concluding you've passed.
Also note CrUX operates on a 28-day rolling window. Fixes do not appear immediately — expect roughly a month before improvements fully register, and don't judge a deployment's impact after a week.
Where to focus in 2026
Rather than chasing a perfect score across every page:
- Fix genuinely broken experiences first — layout shift on above-the-fold content, render-blocking scripts delaying interactivity, unoptimised hero images.
- Prioritise your highest-traffic and highest-converting templates, not your entire site uniformly. Core Web Vitals are assessed per URL, but effort should follow commercial value.
- Audit third-party scripts against INP specifically. Tag managers, chat widgets, consent banners and A/B testing tools are the most frequent causes of INP failure, and they're often the easiest to defer or remove.
- Treat Core Web Vitals as a user experience and conversion metric first, and an SEO metric a distant second. That framing is both more accurate and easier to get budget for.