Core Web Vitals explained for business owners (LCP, INP, CLS)

Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors: how fast the main content appears (LCP), how quickly the page responds to clicks and taps (INP), and how much the layout jumps around while loading (CLS). Good scores are one of Google's page experience signals, though relevance matters far more.

The three metrics in plain English

Google's web.dev documentation defines each metric and the thresholds for "good". Here they are without the jargon.

Anything between good and poor is labeled "needs improvement".

Google measures these at the 75th percentile of real page visits. In practice, that means a page passes a metric when at least three out of four visits meet the "good" threshold. A fast experience on your office laptop does not count for much if most of your visitors are on mid-range phones.

INP replaced an older metric, First Input Delay (FID), as a Core Web Vital in March 2024, according to Google. If an old report mentions FID, it is out of date.

How much do Core Web Vitals affect rankings?

Google says Core Web Vitals are used by its ranking systems as part of page experience, and also says that good page experience alone does not guarantee top rankings. Relevance and helpful content matter more. Google's own documentation is clear that a page with great content can still rank well with average page experience.

So treat Core Web Vitals as:

• A tiebreaker between pages of similar quality
• A real driver of conversions, because slow and jumpy pages lose visitors
• A sign of technical health that often reveals bigger problems

Do not treat them as the main reason a page is or is not ranking unless the scores are very poor.

Field data versus lab data

This trips up a lot of teams.

A Lighthouse score of 95 does not mean your field data passes. A score of 60 does not mean your field data fails. Use field data to decide if there is a problem and lab tools to find the cause. Low-traffic pages may not have enough field data to report, in which case Search Console groups them with similar pages or shows nothing.

What usually causes poor LCP

1. Huge hero images. A 3 MB photo on a homepage is common. Compress it, serve modern formats such as WebP or AVIF, and size it for the screen.
2. Slow server response. Cheap hosting, no caching, or heavy server-side work before the page is sent.
3. Render-blocking resources. Large CSS and JavaScript files that must load before anything shows.
4. Lazy-loading the main image. Lazy loading is great for images further down the page, but the main above-the-fold image should load right away.
5. Fonts and content that only appear after JavaScript runs.

Fixes that often help: compress and correctly size the main image, give it high fetch priority, use a CDN, enable caching, and cut unused CSS and scripts.

What usually causes poor INP

INP is about the browser being too busy to respond. Typical causes:

• Too many third-party scripts (chat widgets, tag managers loading many tags, heatmaps, ad pixels)
• Large JavaScript bundles that run long tasks on the main thread
• Heavy work triggered by clicks, such as re-rendering a large part of the page
• Sliders, popups and menus built with inefficient code

Fixes that often help: remove scripts you no longer use, load non-essential scripts after the page is interactive, break long tasks into smaller ones, and test on a real mid-range Android phone, not only a fast desktop.

What usually causes poor CLS

• Images and videos without set width and height, so the browser does not reserve space
• Ads, embeds and cookie banners that push content down after loading
• Web fonts that swap in and change text size
• Content injected above existing content, such as a promo bar that appears late

Fixes that often help: always set image dimensions or aspect ratios, reserve space for embeds and banners, and use overlay banners instead of ones that push the page down.

A practical order of work

If you are a business owner handing this to a developer or agency, this order tends to make sense:

1. Open Search Console, go to Core Web Vitals, and check mobile first. Note which URL groups are poor.
2. Run the worst examples through PageSpeed Insights and look at the diagnostics.
3. Fix the templates, not single pages. Most sites have a handful of templates (homepage, service page, blog post). Fixing a template fixes every page that uses it.
4. Start with the metric marked poor on the most important templates.
5. Remove unused third-party scripts. This is often the cheapest win.
6. After shipping fixes, use the "Validate fix" button in Search Console. Field data is collected over a rolling 28-day window, so improvements take weeks to show.

Questions to ask your developer or agency

• Are we looking at field data or only Lighthouse scores?
• Which templates fail, and on mobile or desktop?
• Which third-party scripts load on every page, and do we still need them?
• Is the main image on each template compressed, correctly sized and not lazy-loaded?
• Do all images and embeds have reserved space?
• How will we confirm the fix worked in field data?

Platform notes

Site builders such as Webflow, Wix, Squarespace and Shopify handle hosting and some optimization for you, but heavy themes, apps and embedded widgets can still cause poor scores. WordPress sites vary widely depending on theme, plugins and hosting. Custom-built sites using frameworks like React or Next.js can be very fast or very slow depending on how they are built. The platform matters less than what you load on it.

Where this fits in SEO overall

Core Web Vitals are one part of technical SEO. Crawling, indexing, internal links and content quality usually matter more for rankings. Our technical SEO checklist puts them in context, and our guide on what a real SEO audit includes shows how to weigh them against everything else. Faster pages also tend to convert better, which is why we look at speed alongside B2B website conversion rate.

If you want to know whether page speed is actually holding your site back, or whether the bigger issue is elsewhere, book a business audit. We will check your field data on the call and tell you honestly where it ranks among your priorities.