Core Web Vitals Explained for Business Owners: LCP, INP and CLS, What Counts as Good and How to Improve Them

On this page

1. The three Core Web Vitals and their thresholds
2. What each metric means in practice
3. Field data vs lab data
4. How the 75th percentile and 28-day window work
5. Reading the Core Web Vitals report in Search Console
6. Do Core Web Vitals affect Google rankings?
7. Common WordPress causes, and where to fix them
8. A sensible order of work
9. Core Web Vitals on Indian mobile traffic
10. Quick check: which metric is failing, and where?
11. When to get help
12. FAQs

Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors: Largest Contentful Paint (LCP) for loading, good at 2.5 seconds or less; Interaction to Next Paint (INP) for responsiveness, good at 200 milliseconds or less; and Cumulative Layout Shift (CLS) for visual stability, good at 0.1 or less. They're measured on real Chrome users over the previous 28 days, and a page passes when all three are good for at least 75% of visits.

You can see your results in PageSpeed Insights and in Search Console's Core Web Vitals report. Below is what each metric means, how the measurement works, how to read the report and what usually causes problems on WordPress sites. Core Web Vitals fixes for LCP, INP and CLS are part of my WordPress speed optimization service, with a before-and-after report.

The three Core Web Vitals and their thresholds

Metric	What it measures	Good	Needs improvement	Poor
LCP: Largest Contentful Paint	How long the main content, usually the hero image or main heading, takes to appear	2.5 s or less	2.5 to 4 s	Over 4 s
INP: Interaction to Next Paint	How quickly the page visibly responds to taps, clicks and key presses	200 ms or less	200 to 500 ms	Over 500 ms
CLS: Cumulative Layout Shift	How much content unexpectedly jumps around while the page is used	0.1 or less	0.1 to 0.25	Over 0.25

Mobile and desktop are assessed separately. Most sites do worse on mobile, which is also where most of their visitors are.

What each metric means in practice

LCP: does the main content appear quickly?

LCP is the moment the largest image or block of text in the visible part of the screen finishes rendering. On most business sites that's the hero image, a slider, or the main heading. A slow LCP usually comes from one of four places: the server taking too long to respond, the browser discovering the image late, the image itself being too heavy, or CSS and JavaScript blocking the page from drawing. How to fix slow LCP shows how to find your LCP element and which of the four is to blame.

INP: does the page respond when someone taps?

INP replaced First Input Delay as a Core Web Vital in March 2024. Where First Input Delay only looked at the first tap, INP looks at interactions throughout the visit, such as opening a menu, choosing a product option or submitting a form, and reports one of the slowest. Poor INP almost always means the browser is busy running JavaScript: chat widgets, trackers, sliders, heavy page builder layouts or plugins doing work on every page. See how to improve INP.

CLS: does the layout stay still?

CLS adds up unexpected movements of content, such as text pushed down by an image without dimensions, a late-loading banner or a font swap. Movement that happens straight after someone taps, such as an accordion opening, doesn't count. Bad CLS is why people tap the wrong button. See how to fix CLS on WordPress.

Field data vs lab data

This is the part that confuses most people, because two tools can show completely different numbers for the same page.

	Field data	Lab data
Source	Real Chrome users, through the Chrome UX Report (CrUX)	A single simulated visit, using Lighthouse
Where you see it	Top of PageSpeed Insights, Search Console	Lower part of PageSpeed Insights, Lighthouse, GTmetrix
Time period	The previous 28 days	The moment you run the test
Includes INP?	Yes	No; Total Blocking Time is used as a stand-in
What Google uses	This one	Not directly; it's a diagnostic tool

The lab performance score from 0 to 100 isn't a Core Web Vital. It's useful for finding problems and checking fixes, but a page can pass Core Web Vitals with an orange score, or fail them with a green one. Website speed test tools explained covers PageSpeed Insights, Lighthouse, GTmetrix and WebPageTest in detail.

How the 75th percentile and 28-day window work

Google doesn't use your average visitor. It takes the value that 75% of page visits meet or beat, so a page passes LCP only if at least three-quarters of visits saw the main content within 2.5 seconds. That's deliberate: it means people on slower phones and networks count.

The data covers a rolling 28 days. When you fix something today, each new day of good visits replaces an old day of bad ones, so field data improves gradually and fully reflects a fix only after about four weeks. That's normal, and it's why the lab test is the place to confirm a fix straight away.

Field data also needs enough traffic. If a page doesn't have enough Chrome visits, PageSpeed Insights shows data for your whole domain instead, or no field data at all. Many small business sites only have domain-level data, which is still useful.

Reading the Core Web Vitals report in Search Console

1. Open Search Console and go to Core Web Vitals, in the Experience section at the time of writing.
2. Choose the mobile or desktop report. Start with mobile.
3. Look at the counts of URLs rated Poor, Need improvement and Good. A URL's rating comes from its worst metric.
4. Open an issue such as "LCP issue: longer than 2.5s (mobile)". Search Console groups similar pages together, such as all blog posts or all product pages, and shows example URLs.
5. Test an example URL in PageSpeed Insights to find the cause. Fixing the template usually fixes the whole group.
6. After fixing, click Validate fix. Search Console then monitors the group over the next 28 days.

If the report says there isn't enough data, your site doesn't yet have enough Chrome traffic. Use PageSpeed Insights' lab results in the meantime. For the rest of Search Console, see Search Console reports explained.

Do Core Web Vitals affect Google rankings?

They're part of Google's page experience signals, but relevance and content quality matter far more. Google has said good Core Web Vitals align with what its ranking systems reward, but a fast page with weak content won't outrank a slower page that answers the search better. Where Core Web Vitals clearly matter is with visitors: slow, jumpy, unresponsive pages lose enquiries and sales, whatever their ranking.

Common WordPress causes, and where to fix them

Symptom on WordPress	Metric affected	Typical fix
Long pause before anything appears	LCP	Page caching, better hosting, fewer slow plugins
Large hero image or slider	LCP	Resize, compress and serve WebP; don't lazy-load the top image; replace sliders with one image
Many CSS and JavaScript files in the page head	LCP	Defer non-critical scripts, remove unused CSS
Chat widgets, trackers, ad scripts	INP	Remove what isn't used, delay the rest until interaction
Heavy page builder layouts, mega menus	INP	Simpler layouts, fewer widgets and add-ons
Images without width and height	CLS	Set dimensions so space is reserved
Cookie banners, offer bars, late-loading embeds	CLS	Reserve space, or overlay rather than push content down
Web fonts swapping late	CLS, LCP	Fewer font files, preload the main font

If the slow part is server response, how to reduce TTFB explains caching, PHP and hosting. For the full list of causes, see why is my WordPress site slow?

Fonts affect both LCP and layout shift. Small changes such as fewer weights and self-hosting can reduce font load without changing the design.

A sensible order of work

1. Check the field data in PageSpeed Insights and Search Console, mobile first.
2. Pick the worst metric on your most important page type, such as service pages or product pages.
3. Fix server response and caching first, because they affect every metric and every page.
4. Then fix the LCP element, scripts, and layout shifts, in order of impact.
5. Confirm each fix with a lab test, check the pages still work, then let field data catch up over 28 days.

Test on a real mid-range Android phone on mobile data as well. Many Indian visitors browse on budget phones and variable connections, and that's exactly the audience the 75th percentile captures; see website speed on Indian mobile networks.

Core Web Vitals on Indian mobile traffic

For most Indian business sites, the majority of visitors arrive on mid-range Android phones over mobile data. That is where Core Web Vitals usually fail, even when the site feels quick on an office laptop on Wi-Fi. A few patterns come up again and again:

• LCP suffers from large hero images and sliders, image-heavy page builders and slow shared hosting that takes too long to send the first byte.
• INP suffers from heavy JavaScript: chat widgets, WhatsApp buttons loaded as scripts, pop-up builders, multiple tracking tags and large theme bundles that keep the phone busy.
• CLS suffers from banners and cookie notices that push content down, ads without reserved space and web fonts that swap late.

Test the way your visitors browse. In PageSpeed Insights, read the mobile tab first. In Chrome DevTools, use network and CPU throttling to approximate a slower phone. Then compare against the field data in Search Console, which reflects your real audience.

If your Shopify store fails Core Web Vitals, the same principles apply: too many apps adding scripts, oversized images and heavy theme sections. The difference is that on Shopify you mostly fix it by removing apps and simplifying the theme rather than changing hosting.

Quick check: which metric is failing, and where?

In Search Console, open Experience, Core Web Vitals, click Open report for Mobile and click each issue (for example "LCP issue: longer than 2.5s") to see the example URL groups. Test one example URL in PageSpeed Insights: the field data at the top confirms the problem, and the Diagnostics section below points to the element causing it.

If visitors are spread across regions, a CDN can serve static files from servers closer to them.

When to get help

Get help when pages stay Poor or Needs improvement after the basics, or when fixes risk breaking the layout, forms or checkout. WordPress speed optimization includes a full audit, fixes for LCP, INP and CLS, testing after every change and a before-and-after report. To start, send your website address.

For a quick LCP win, convert large hero images with the free PNG and JPG to WebP converter.

FAQs

What are good Core Web Vitals scores?

LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less, each met by at least 75% of page visits. A page passes the assessment when all three are good.

Why does PageSpeed Insights say there's no field data for my page?

The page doesn't have enough visits from Chrome users in the last 28 days. PageSpeed Insights then shows data for your whole domain, or nothing. The lab test below still helps you find and fix problems.

How long does it take for Core Web Vitals to update after a fix?

Up to about four weeks, because field data covers a rolling 28 days. Lab tests show the improvement immediately; Search Console follows as new visits replace old ones.

Do I need a PageSpeed score of 100?

No. The lab score isn't a Core Web Vital, and chasing 100 can mean removing useful features. Aim to pass Core Web Vitals for real visitors, especially on mobile.

What happened to First Input Delay?

Interaction to Next Paint replaced First Input Delay as a Core Web Vital in March 2024. INP measures responsiveness across the whole visit, not just the first tap, so it's harder to pass.

Why do my Core Web Vitals pass on desktop but fail on mobile?

Phones have slower processors and often slower connections, so heavy images and JavaScript hurt them far more. Google reports mobile and desktop separately, so fix the mobile issues first.