Core Web Vitals (CWV) still influence Google rankings, but only as a tiebreaker between pages of similar relevance, not as a primary signal. For most business-to-business (B2B) sites, fixing them moves conversion and crawl efficiency far more than it moves position.
The short version
- Google ranks relevance and content quality first; Core Web Vitals only break ties between results that are already close.
- The three metrics are Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness), and Cumulative Layout Shift (visual stability).
- Interaction to Next Paint replaced First Input Delay in March 2024, so any audit built around First Input Delay is measuring a retired metric.
- A green lab score in a tool like Lighthouse does not move rankings; only field data from real Chrome users counts toward the ranking consideration.
- The dependable payoff of performance work is lower bounce and higher conversion, not a ranking jump. Fund it as a revenue project.
Relevance decides rankings; Core Web Vitals only break ties
Google has been consistent on this for years: page experience is one of many signals, and it does not override relevance. If a slower page answers the query better, it still wins. Core Web Vitals come into play when two results are close enough that Google needs a reason to prefer one. That is the honest ceiling on what performance work can do for position, and most teams set the expectation far too high.
This matters for how you pitch the work internally. If you tell a vice president that shaving a second off load time will lift you three spots, you will be wrong often enough to lose credibility. The accurate pitch is that performance protects the rankings you already earn and improves what happens after the click. Google's own page experience guidance frames it the same way: strong page experience supports good content, it does not replace it.
The three metrics measure loading, responsiveness, and stability
Each Core Web Vital maps to a different moment in how a page feels. Largest Contentful Paint (LCP) measures how long the main content takes to render, with a good score at or under 2.5 seconds. Interaction to Next Paint (INP) measures how fast the page responds to taps and clicks, with a good score at or under 200 milliseconds. Cumulative Layout Shift (CLS) measures how much the layout jumps while loading, with a good score at or under 0.1. Google reads the 75th percentile of your real traffic, so you pass only when roughly three of every four visits clear the bar.
The one change that still trips up audits is responsiveness. In March 2024, Interaction to Next Paint replaced First Input Delay as the responsiveness vital. First Input Delay only measured the delay before the very first interaction, which almost everything passed. Interaction to Next Paint measures responsiveness across the whole visit, which is harder and more honest. If a performance report you are handed still lists First Input Delay, it is working from a metric Google no longer uses, and you should send it back. The current thresholds are documented on web.dev.
Field data is what counts, not your lab score
The ranking consideration uses field data, not the lab score you see when you run a one-off test. Lab tools like Lighthouse simulate a single load on a throttled connection, which is useful for debugging but is not what Google scores. The data that counts comes from the Chrome User Experience Report (CrUX), which aggregates real page loads from opted-in Chrome users over a rolling 28-day window. That gap is why a page can show green in the lab and fail in the field, or the reverse.
The practical consequence is to stop celebrating a 98 in PageSpeed Insights. Look at the field section of the same report, or pull CrUX directly, and always segment mobile from desktop. I have seen plenty of sites post a beautiful lab score while real mobile users on mid-range phones sat in the red on Interaction to Next Paint, because of a heavy tag manager and three chat widgets. The lab never saw the problem, because the lab does not carry your third-party load.
What Core Web Vitals actually move is conversion
When I ran performance work for a legal-services nonprofit last year, the rankings barely moved. What moved was the donation flow. The donation page had a Largest Contentful Paint over five seconds on mobile because of an uncompressed hero image and a render-blocking font, and the form shifted under people's thumbs as a third-party script loaded late, which is a Cumulative Layout Shift problem. We compressed and preloaded the image, preloaded the font, and reserved space for the injected element. Load time dropped under two seconds and completed mobile donations climbed. The keyword positions did not change in any way I would stake a report on.
That is the pattern on almost every project. Performance is a conversion lever wearing a search engine optimization (SEO) costume. Treat it as a revenue project and the business case writes itself: faster pages lose fewer people between the ad click and the form submit. Treat it as a rankings project and you will overpromise, underdeliver, and struggle to get the next performance ticket funded.
Where I spend the performance budget first
I fix these in a fixed order, because the effort-to-impact ratio is predictable. Largest Contentful Paint comes first, because it is usually the cheapest win and the most visible: compress and correctly size the hero image, serve it in a modern format, preload it, cut render-blocking scripts and fonts, and get server response time down. Interaction to Next Paint comes second and is almost always a JavaScript problem: break up long tasks, defer what the first screen does not need, and audit third-party tags, which are the usual culprit. Cumulative Layout Shift comes last and is the most mechanical: set explicit width and height on images and embeds, reserve space for anything injected late, and use font loading settings that do not reflow the page.
If you are already planning a replatform for next year, fold this into that scope rather than running it twice. The architecture decisions you make during a migration, from image handling to script loading to font strategy, determine your Core Web Vitals far more than any after-the-fact tuning. I keep a replatform checklist that treats performance as a build requirement rather than a cleanup task.
What this does not cover
This is scoped to the three Core Web Vitals and their effect on Google ranking and conversion. It does not cover the rest of Google's page experience guidance, which also includes serving over HTTPS and avoiding intrusive interstitials. It does not get into the measurement quirks of single-page applications, where soft navigations are counted differently and can distort your field data. And it says nothing about how answer engines weigh speed, because ChatGPT, Perplexity, and Google's AI surfaces do not publish a Core Web Vitals equivalent. If your traffic is shifting toward those engines, speed still helps the human who clicks through, but it is not a documented ranking input the way it is in classic Search.
Frequently asked questions
Do Core Web Vitals directly improve my Google rankings?
Not on their own. They act as a tiebreaker between pages of similar relevance, so they can protect or nudge a position but rarely create a large jump. Expect the clearer gains in conversion and bounce rate.
What is a good Core Web Vitals score?
At the 75th percentile of your real traffic: Largest Contentful Paint at or under 2.5 seconds, Interaction to Next Paint at or under 200 milliseconds, and Cumulative Layout Shift at or under 0.1. You have to clear all three to pass.
Why does my PageSpeed Insights lab score not match my ranking?
Because Google scores field data from real Chrome users, not the lab simulation. A high lab score paired with poor field data is common, usually caused by third-party scripts the lab test does not fully load. Read the field section of the report, not the lab gauge.
Is First Input Delay still a Core Web Vital?
No. Interaction to Next Paint replaced First Input Delay in March 2024. If a tool or audit still reports First Input Delay as a current vital, it is out of date.
Run this on your own site
If you want me to pull your site's field Core Web Vitals from the Chrome User Experience Report and tell you which of the three is actually costing you conversions, book a 20-minute read-out.