Core Web Vitals: What Still Matters and What Doesn't
Core Web Vitals are a real but modest part of page experience. Here is what INP replaced, what thresholds apply, what Google says about ranking, and where to spend engineering time.
Core Web Vitals get treated as a pass/fail gate in a lot of SEO advice. The reality is more nuanced: they measure real aspects of user experience, Google's ranking systems take page experience into account, and they are not the dominant factor. This article sticks to what Google and the web.dev team document, and avoids invented ranking statistics.
The three metrics
| Metric | Measures | "Good" threshold (75th percentile of page loads) |
|---|---|---|
| Largest Contentful Paint (LCP) | How quickly the main content appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | Responsiveness to interactions across the visit | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Visual stability, unexpected layout movement | 0.1 or less |
Thresholds are assessed on real-user data at the 75th percentile, separately for mobile and desktop.
The metric that replaced FID
If you learned Core Web Vitals at launch, you learned First Input Delay (FID). INP replaced FID as a Core Web Vital in March 2024. FID measured only the delay before the first interaction began processing. INP considers interactions across the whole visit and reports a value near the slowest, so it surfaces problems such as a sluggish menu, filter or modal after the page has loaded. Sites that passed FID can fail INP.
What Google says about ranking
Google states that its core ranking systems seek to reward content that provides a good page experience, and that Core Web Vitals are used by those ranking systems. It also says that a good page experience does not override the importance of having great, relevant content, and that there is no single page experience "score" or guarantee. In practice:
- Fixing a poor experience is worthwhile for users and removes a disadvantage.
- Shaving the last 100 milliseconds from an already good LCP at the expense of content, links or technical fixes is rarely the best use of time.
- Be sceptical of any claim of precise ranking correlations unless the methodology is published. We do not publish one, so we do not make such claims.
Field data vs lab data
- Field data comes from real users. Google's Chrome User Experience Report (CrUX) is the source for the Core Web Vitals report in Search Console and for the field section of PageSpeed Insights. This is the data that reflects real experience.
- Lab data (Lighthouse and similar) is a simulated test: useful for debugging, not the definition of your score.
Chasing a perfect Lighthouse number while real-user data is poor misses the point.
Where time is usually wasted
- Optimising a lab score that differs from real-user conditions.
- Obsessing over images while ignoring third-party scripts. Analytics tags, chat widgets, ad scripts and consent tools frequently contribute heavily to slow interactions and layout shifts. Audit them before micro-optimising.
- Testing only on fast office networks and desktops. Mobile conditions are where many sites fail.
- Treating mobile and desktop as one result. They are assessed separately.
A practical priority order
- Find real problems. Open Search Console's Core Web Vitals report and PageSpeed Insights field data. Focus on URL groups marked Poor.
- Fix the dominant cause per metric.
- LCP: slow server response, large hero images, render-blocking resources, lazy-loading the LCP image by mistake.
- INP: long JavaScript tasks, heavy third-party scripts, expensive event handlers.
- CLS: images and embeds without dimensions, late-injected banners and fonts.
- Audit third-party scripts and remove what you do not need.
- Test on real mobile devices or throttled connections.
- Re-check field data after changes. It updates over a rolling window, so allow weeks.
What Bizsenti AutoSEO does and does not do here
The technical SEO audit records response time, compression, caching headers and image problems (large images, missing lazy loading) on sampled pages. It does not measure Core Web Vitals; use Search Console and PageSpeed Insights for that.
Common mistakes
- Treating CWV as the whole of technical SEO.
- Ignoring INP because FID used to pass.
- Fixing images first when scripts are the cause.
- Reading a single lab report as truth.
A Core Web Vitals triage table
| Symptom | Likely area | First check |
|---|---|---|
| Hero image appears late | LCP | Image size, format, priority, server response |
| Buttons feel sticky after load | INP | Long JavaScript tasks, third-party scripts |
| Text jumps as the page loads | CLS | Missing image dimensions, injected banners, fonts |
| Fine on desktop, poor on mobile | All | Mobile-specific layout and scripts |
A simple improvement log
Record the metric, the URL group, the suspected cause, the change, the date and the follow-up reading. Because field data updates on a rolling window, you need dates to connect changes to results.
When not to worry
If your field data already shows good values for all three metrics on your key templates, invest elsewhere. Core Web Vitals are one component of page experience, and Google says relevance and content quality remain more important.
FAQs
Are Core Web Vitals a ranking factor? Google says they are used by its ranking systems as part of page experience, alongside much stronger signals such as relevance and content quality.
What are the thresholds? LCP 2.5 s or less, INP 200 ms or less, CLS 0.1 or less at the 75th percentile.
Why does PageSpeed Insights show two sets of numbers? Field data (real users) and lab data (a simulated test). Prioritise field data.
How long until fixes show in Search Console? The report is based on a rolling window, so expect weeks.
The takeaway
Core Web Vitals are worth fixing properly because they affect real users, but they remove a disadvantage rather than create an advantage. A technically perfect site with thin content and no relevant links will still lose to a slightly slower site with genuinely better content.
Sources
Put this into practice with Bizsenti AutoSEO
Track rankings, run audits, monitor links and send reports from one workspace. 7-day free trial, no credit card required.
Start free trial