Core Web Vitals are three metrics Google uses to measure how a page feels to use: how fast the main content appears, how quickly the page responds to interaction, and how much the layout jumps around while loading. They are a genuine ranking signal, but a modest one. They will not lift a page that does not deserve to rank, and they will not sink one that does.
That nuance matters, because Core Web Vitals get treated either as the whole of SEO or as irrelevant. Neither is right.
Here is what each metric actually measures, how much weight to give them, and what actually moves the numbers on a real business website.
Page experience is one part of our technical SEO work, alongside crawling, indexation and site structure.
The Three Core Web Vitals Metrics, Explained
Each core web vital measures a different part of the loading experience, and they fail for different reasons.
Largest Contentful Paint (LCP) measures how long the initial page load takes before the biggest visible element finishes rendering. Usually that is a hero image, a heading, or a video poster. It answers "how long before the page looks like something." Good is under 2.5 seconds.
Interaction to Next Paint (INP) measures how quickly the web page visually responds to user input. Click a menu, tap a button, type in a field: how long before something visibly happens. Good is under 200 milliseconds. INP replaced First Input Delay, and it is stricter, because First Input Delay looked only at the first interaction while INP looks at all user interactions across the visit.
Cumulative Layout Shift (CLS) measures visual stability of the page layout. It is the metric behind the experience of reaching for a button and having the page shove it somewhere else at the last moment. Good is under 0.1.
Together these three core web vitals metrics describe page experience: does the page appear quickly, respond promptly, and stay still. Each core web vital fails for a different reason, which is why a single fix rarely moves all three.
Are Core Web Vitals Ranking Factors, and Why Are Core Web Vitals Important?
Less than most people selling page speed services suggest, and more than nothing.
Google has been consistent that page experience sits among its ranking factors as a tiebreaker rather than a primary one. Relevance and content quality come first. If two pages are comparably useful, the faster and more stable one has an advantage. If one page is far more useful, it wins regardless of its LCP.
The practical read: Core Web Vitals are worth fixing, but they are the wrong place to start if your content does not match search intent or your site has no authority. We cover that ordering in why your website isn't ranking.
The stronger argument for fixing them is not rankings at all. Slow, unstable pages lose conversions. That effect is direct, measurable, and larger than the ranking effect.
Lab and Field Data: Which One Google Uses
This is the distinction that confuses most people looking at their scores.
Lab data is a simulated test run on demand, in a controlled environment. PageSpeed Insights shows this at the top, and it is useful for debugging because it is repeatable.
Field data is what real users actually experienced, collected in the Chrome User Experience Report over the previous 28 days. This is the core web vitals data Google uses for the page experience signal.
Lab and field data frequently disagree, and when they do, field data is the one that counts. A site can score beautifully in a lab test on a fast connection and perform badly for real visitors on mid-range phones. If your field data is missing entirely, that usually means the page does not have enough traffic to report on.
Check both. Fix for the field.
Where to Measure: PageSpeed Insights, Search Console and a Site Audit
PageSpeed Insights is a free tool that gives you both field and lab data for any URL. Start here.
Google Search Console has a core web vitals report covering your whole site, grouped by URL pattern. This is more useful than testing pages one at a time, because it shows you which templates are failing rather than which individual pages.
Chrome DevTools Performance panel is where you diagnose long tasks and find what is actually blocking the main thread.
A full site audit should include all three, because each answers a different question about your site's core web vitals.
What Actually Fixes Largest Contentful Paint
Largest Contentful Paint is usually an image problem or a server problem.
Serve properly sized, modern-format images. The single most common cause of poor LCP on business websites is a hero image exported at full camera resolution. Convert to WebP, size it to its display dimensions, and compress.
Do not lazy-load the hero. Lazy loading is good practice for images below the fold and actively harmful for the one image that defines your LCP.
Preload the LCP element so the browser fetches it early rather than discovering it late.
Fix server response time. If time to first byte is slow, nothing downstream can be fast. Decent hosting and page caching solve most of this.
Reduce render-blocking resources. Stylesheets and scripts in the head delay everything behind them.
What Actually Fixes Interaction to Next Paint
Interaction to next paint is a JavaScript problem almost every time.
Long tasks block the main thread, so when a user interacts, the browser cannot respond until it finishes what it is doing. The fixes are about doing less work, and doing it later.
Remove plugins and third-party scripts you are not using. On a typical WordPress site this is the highest-value change available, and it is free. Every chat widget, heatmap, popup builder and analytics tag adds main-thread work.
Defer scripts that are not needed for the initial render. Break up long-running tasks. Be sceptical of page builders that ship large JavaScript bundles for layouts that could be CSS.
What Actually Fixes CLS
Cumulative layout shift is almost always something that loaded late and pushed content down.
Set explicit width and height on images and video so the browser reserves the space before the file arrives.
Reserve space for ads, embeds and iframes rather than letting them expand into the page.
Load fonts carefully. A web font swapping in at a different size shifts everything around it. Use font-display: swap with a fallback that closely matches your web font's metrics.
Never insert content above existing content after load. Cookie banners, notification bars and promotional strips are the usual offenders, and they are the reason CLS is often worst on the homepage.
Common Mistakes We See
Chasing a score of 100. The core web vitals metrics are a diagnostic, not a target. A page that passes all three thresholds is done; the difference between passing and perfect is rarely worth the engineering.
Installing a performance plugin and stopping. Caching plugins help with server response and little else. They do not fix an oversized hero image or a bloated script.
Optimising the homepage only. Most organic entrances land on interior pages. Fix the templates, not the one page you look at most.
Testing on desktop. Google evaluates mobile. Test on a mid-range phone on a normal connection, which is where real visitors actually are.
Where This Sits in the Priority List
If you are deciding where to spend effort, page experience belongs after the fundamentals and before the refinements.
Get indexed. Match search intent. Build content worth ranking. Then fix your website's core web vitals, because at that point they are a genuine differentiator against comparable competitors, and because the conversion benefit stands on its own regardless of what Google does with the signal.
Our technical SEO service covers this alongside crawling, indexation and site architecture, since they are rarely broken in isolation.
Get Your Numbers Looked At Properly
If your core web vitals seo numbers are failing and you have already tried a caching plugin, the remaining problems are usually specific and findable rather than mysterious.
Talk to us and we will tell you what is actually slowing your pages down and whether it is worth fixing for your situation.
Frequently Asked Questions
Are Core Web Vitals a ranking factor?
Yes, as part of Google's page experience signals, but a modest one. They act as a tiebreaker between pages of comparable relevance and quality rather than overriding either.
What are good Core Web Vitals scores?
Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. These thresholds are measured at the 75th percentile of real user visits.
Why does PageSpeed Insights show different results each time?
The lab test at the top of the report is a simulation and varies run to run. The field data below it comes from real Chrome users over 28 days and is far more stable. Field data is what Google uses.
Will a caching plugin fix my Core Web Vitals?
Partly. Caching improves server response time, which helps LCP. It does not fix oversized images, heavy JavaScript affecting INP, or layout shifts from unsized elements.
Should I fix Core Web Vitals before anything else in SEO?
Usually not. If your pages are not indexed, do not match search intent, or the site has no authority, those problems dominate. Fix page experience once the fundamentals are in place.
