Core Web Vitals occupy a strange place in SEO. Everyone knows they matter, nobody can point to the traffic they gained by fixing them, and yet every site I have improved has converted better afterwards.
That is the honest framing. As a ranking signal they are a tie-breaker. As a business input they are worth more than that, because a fast site sells more.
So fix them for the second reason and treat the first as a bonus.
Here is what the three metrics actually measure, what usually breaks them, and the shortest route to passing.
Quick Info
The Three Metrics
Largest Contentful Paint
How long until the biggest visible element in the viewport has rendered. It is the closest single number to how quickly the page feels like it has arrived. Pass at 2.5 seconds or under, for the seventy-fifth percentile of real visits.
Interaction to Next Paint
How long between a user interacting and the page visibly responding, measured across the whole visit rather than just the first tap. It replaced First Input Delay and it is a much harder test, because it catches the sluggishness that appears halfway down a page. Pass at 200 milliseconds or under.
Cumulative Layout Shift
How much the layout jumps about while loading. This is the one users complain about without knowing its name, usually while trying to tap a button that moved. Pass at 0.1 or under.
All three are measured on real visits, which is why lab tools and field data disagree so often. Field data is the one Google uses. Lab data is how you diagnose it.
What Changed Recently
Two shifts worth knowing about.
First, INP has bedded in as the responsiveness metric, and it has been much less forgiving than its predecessor. Sites that comfortably passed First Input Delay routinely fail INP, because the old metric only looked at the first interaction and effectively ignored everything after it.
Second, the emphasis has moved further towards field data over lab scores. A ninety-something PageSpeed score with failing field vitals means your test conditions are nicer than your users' conditions. Trust the users.
The practical consequence is that JavaScript weight now costs you more than it used to, and third-party scripts are the usual culprit.
Fixing LCP
Almost every LCP failure traces to one of four causes. Work through them in this order.
On WordPress sites specifically, a good caching plugin plus proper image handling fixes LCP roughly nine times in ten, and I have never needed anything more exotic on a small business site.
Fixing INP
INP is a JavaScript problem in almost every case. The main thread is busy and cannot respond.
The diagnosis is a performance recording in DevTools while you interact with the page. Look for long tasks, then look at what owns them.
The single highest-return action here is removing scripts. Not optimising them. Removing them.
Fixing CLS
This is the easiest of the three and there is no excuse for failing it.
Half an hour with these five items usually takes a failing CLS score to passing.
How Much It Actually Matters
I will not pretend vitals are a major ranking lever. Between two comparable pages the faster one has an edge, and that is roughly the size of it.
The reason to do the work is downstream. Faster pages get further through the funnel, mobile users on poor connections stop abandoning, and the crawl gets cheaper, which on a large site means more of your content gets seen.
Treat vitals as a conversion project that happens to help SEO, not the other way round.
Framed that way, the work is easy to justify and easy to measure, because the metric you report is revenue per session rather than a coloured bar in a dashboard.
Frequently Asked Questions
Yes, as part of the page experience signals, but a modest one. They act more as a tie-breaker between comparable pages than as a primary factor.
PageSpeed's lab score is a simulated test on one device. Search Console shows field data from real visits at the seventy-fifth percentile. Field data is what counts.
Field data uses a twenty-eight day rolling window, so allow a full month after deploying fixes before judging the result.
Good hosting plus a caching plugin plus properly sized modern-format images. That combination fixes most LCP failures without touching code.
Considerably. FID measured only the first interaction. INP looks across the whole visit, which exposes JavaScript problems that used to go unnoticed.
To get the page experience benefit, yes, all three need to be in the good range. For business reasons, fix whichever is worst first.
Before You Go
If you only do one thing after reading this, open the Core Web Vitals report in Search Console and look at which URL group is failing rather than which page. Template-level fixes are where the leverage is.
My speed checklist and the hosting and caching setups I recommend are in the resources section and on the tools page.
If your site is slow and you would rather not spend a fortnight in DevTools, get in touch.
Delete a script, thank me later, Tariq
I'm a marketing consultant, entrepreneur and content creator. I help businesses grow through practical marketing, websites, SEO, content and AI.
More About Tariq →