SERP Master Agency

SEO · 10 min read · Updated Nov 12, 2026

Core Web Vitals Explained: LCP, INP and CLS for Business Owners

Core Web Vitals are three metrics Google uses to measure how real visitors experience your pages: Largest Contentful Paint (LCP) for loading speed, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. Good scores are 2.5 seconds, 200 milliseconds and 0.1 or less (web.dev).

This guide explains each metric in plain English, how much they matter for rankings, how to check your scores, and which fixes to make first so your effort turns into a better experience for the people who become your customers.

Key takeaways

  • Core Web Vitals are three Google metrics for real-world page experience: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability).
  • A page passes when 75% of visits get an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less.
  • Google confirms Core Web Vitals are used by its ranking systems, but relevance comes first, so they help most when competing pages are similarly useful.
  • Only 48% of mobile websites passed all three metrics in July 2025, and LCP was the metric most often missed, according to the HTTP Archive Web Almanac.
  • Fix the metric that fails on your most valuable page templates first, then allow about 28 days for Google's field data to reflect the change.

What are Core Web Vitals?

Core Web Vitals are three metrics from Google that measure real visitors' experience of a web page. Largest Contentful Paint measures how fast the main content loads, Interaction to Next Paint measures how quickly the page responds to taps and clicks, and Cumulative Layout Shift measures how much the layout jumps while loading.

Each metric has three bands. Google measures them at the 75th percentile of page loads, split by mobile and desktop, so a page passes only if at least three in four visits meet the good threshold (web.dev).

MetricWhat it measuresGoodNeeds improvementPoor
Largest Contentful Paint (LCP)How fast the biggest image or text block appears2.5 s or less2.5 s to 4.0 sOver 4.0 s
Interaction to Next Paint (INP)How fast the page responds to clicks, taps and key presses200 ms or less200 ms to 500 msOver 500 ms
Cumulative Layout Shift (CLS)How much content moves unexpectedly0.1 or less0.1 to 0.25Over 0.25

Sources: LCP, INP and CLS guides on web.dev.

INP is the newest of the three. It replaced First Input Delay (FID) as a Core Web Vital on March 12, 2024 (Google Search Central blog). Any guide or tool that still reports FID as a Core Web Vital is out of date.

Do Core Web Vitals affect Google rankings?

Yes. Google states that Core Web Vitals are used by its ranking systems. Google also says it always aims to show the most relevant content, even when page experience is poor. In practice, Core Web Vitals rarely lift a weak page above a far more useful one, but they can help when competing pages are similarly helpful.

Google’s page experience documentation makes three points worth knowing (Google Search Central):

  • Core Web Vitals are used by Google’s ranking systems, and Google recommends that site owners achieve good scores.
  • There is no single page experience signal. Core Web Vitals are one input among many.
  • Ranking systems generally evaluate pages one at a time, though Google also has some site-wide assessments.

For a business owner, the ranking effect is only part of the story. A slow page loses visitors before they see your offer, a laggy form frustrates people trying to contact you, and a layout that jumps causes mis-taps on buttons. Those problems cost leads whether or not rankings move.

What is Largest Contentful Paint (LCP) and how do you improve it?

Largest Contentful Paint is the time it takes for the largest image, video or text block in the visible part of the page to appear. A good LCP is 2.5 seconds or less. The usual fixes are smaller, compressed hero images, faster hosting and caching, and removing scripts and styles that block the page from rendering.

The LCP element is usually the hero image, a large banner or the main heading block. Images, video posters, CSS background images and block-level text can all count (web.dev).

Common LCP fixes

  • Compress and resize the hero image. Serve it in a modern format such as WebP or AVIF, at the size it is displayed.
  • Never lazy-load the LCP image. Lazy loading belongs on images further down the page.
  • Speed up the server. Use page caching and, where your host supports it, a content delivery network (CDN).
  • Remove render-blocking code. Defer non-critical JavaScript and trim unused CSS.
  • Cut slow sliders. Carousels often load several large images before the first one shows.

LCP is the metric websites fail most often. Only 62% of mobile websites had a good LCP in July 2025, compared with 77% for INP and 81% for CLS (Web Almanac 2025).

What is Interaction to Next Paint (INP) and how do you improve it?

Interaction to Next Paint measures how quickly a page visibly responds when someone clicks, taps or presses a key, across the whole visit. A good INP is 200 milliseconds or less. Poor INP usually comes from heavy JavaScript, such as page builders, chat widgets, tracking tags and plugins, that keeps the browser busy.

INP looks at all qualifying interactions during a visit, not only the first one, and reports one value for overall responsiveness. Hovering and scrolling do not count (web.dev).

Common INP fixes

  • Audit third-party scripts. Remove tags and widgets nobody uses, and delay the rest until after the page loads.
  • Reduce plugin and page-builder weight. Each add-on can add JavaScript to every page.
  • Break up long tasks. Developers can split heavy JavaScript into smaller chunks so the browser can respond between them.
  • Simplify menus and forms. Mega menus and multi-step forms with heavy validation are frequent offenders on mobile.

Most sites do better on INP than on LCP: 77% of mobile websites and 97% of desktop websites had good INP in July 2025 (Web Almanac 2025). The gap between mobile and desktop shows why you should always test on a phone.

What is Cumulative Layout Shift (CLS) and how do you improve it?

Cumulative Layout Shift measures how much visible content moves unexpectedly while a page loads or is used. A good CLS is 0.1 or less. The usual causes are images and videos without set dimensions, ads and embeds that resize, web fonts that swap in, and banners inserted above existing content.

Layout shifts that happen within half a second of a tap, click or key press are excluded, because the visitor expects the page to change (web.dev). The shifts that count are the ones nobody asked for.

Common CLS fixes

  • Set width and height on images and videos so the browser reserves the space before they load.
  • Reserve space for ads, maps and embeds with a fixed-size container.
  • Load fonts carefully. Preload key fonts and choose fallback fonts with similar sizing.
  • Do not push content down. Cookie banners, promo bars and chat prompts should overlay the page or sit in reserved space.

CLS is the metric where desktop does worse than mobile: 81% of mobile websites passed in July 2025, but only 72% of desktop websites (Web Almanac 2025).

Next step

Failing Core Web Vitals on WordPress?

We test your key pages, fix LCP, INP and CLS issues, then retest and send you a before-and-after report. See current prices on the product page.

Free consultation

Tell us about your business and we’ll recommend a plan or a few fixed-price tasks.

How do you check your Core Web Vitals?

Check Core Web Vitals in PageSpeed Insights for a single URL and in the Core Web Vitals report in Google Search Console for your whole site. Both use field data from real Chrome users, gathered over a rolling 28-day window. Lighthouse lab tests help find causes but cannot measure INP directly.

There are two kinds of data, and mixing them up causes most of the confusion business owners run into.

Data typeWhere you see itWhat it tells you
Field data (real users)PageSpeed Insights (top section), Search Console Core Web Vitals report, Chrome UX ReportWhether real visitors get a good experience. This is what Google assesses.
Lab data (simulated)PageSpeed Insights performance score, Lighthouse, Chrome DevToolsWhy a page is slow, under test conditions. Useful for debugging.

Field data comes from the Chrome User Experience Report, which is a 28-day rolling average updated daily (Chrome for Developers). Lighthouse cannot measure INP and uses Total Blocking Time as a stand-in (web.dev).

What if there is no data for your site?

A page only appears in the Chrome UX Report if it is publicly discoverable and has enough visitors; Google does not publish the exact threshold (Chrome for Developers). Low-traffic sites often see “no data”. In that case, use lab tests on your key templates and fix the problems they find.

Which Core Web Vital should you fix first?

Fix the Core Web Vital that fails on your most valuable page templates first, such as service pages, product pages or the home page. If more than one metric fails, start with LCP, because loading problems affect every visitor. Fix whole templates instead of single pages, since one template change can repair hundreds of URLs at once.

At SERP Master, we use a simple template-first rule: group URLs by template, find the template that brings the most leads or sales, and fix the failing metric there before touching anything else. Search Console already groups similar URLs together, which makes this easier.

If this failsLikely cause on a typical business siteFirst thing to try
LCP on mobileOversized hero image, slow hosting, render-blocking scriptsResize and compress the hero image; turn on page caching
INP on mobileToo many plugins, tags and widgetsRemove unused scripts; delay chat and tracking scripts
CLS on desktopAds, embeds or images without set dimensionsAdd width and height; reserve space for embeds
All threeHeavy theme or page builder on cheap hostingFix hosting and caching first, then review the theme

If a redesign is coming, build these fixes into the new site rather than patching the old one. Our guide to a website redesign without losing SEO covers what to protect during the switch. Speed is also one step in a wider technical SEO audit checklist, so check that crawling and indexing are healthy before you spend on speed.

Should you fix Core Web Vitals yourself or hire help?

You can fix many Core Web Vitals problems yourself on WordPress with a caching plugin, image compression and removing unused plugins. Hire help when scores stay poor after those basics, when the cause is heavy JavaScript or theme code, or when you cannot risk breaking a site that brings in leads.

What you can do yourself

  • Run PageSpeed Insights on your home page and top service or product page, on mobile.
  • Compress and resize large images, and set image dimensions.
  • Install one reputable caching plugin and remove plugins you no longer use.
  • Keep WordPress, the theme and plugins updated, or order plugin and theme updates if you would rather not do it.

When to bring in help

Script cleanup, font loading and theme-level layout fixes can break forms, menus or tracking if done carelessly. Our Core Web Vitals fixes task for WordPress sites tests key templates on mobile and desktop, makes the changes with a full backup in place, retests the same pages and flags anything that needs a hosting upgrade or developer work. For broader speed work without Core Web Vitals reporting, see WordPress speed optimization, and for ongoing care, our web development services.

Whoever does the work, set expectations: hosting, themes and third-party scripts all limit what is possible, and Google’s field data takes about 28 days to fully reflect a change.

FAQ

Core Web Vitals Explained FAQ

Can’t find your answer? Book a free consultation or email contact@serpmasteragency.com.

No. Interaction to Next Paint (INP) replaced First Input Delay as the responsiveness metric on March 12, 2024, according to Google’s Search Central blog. INP is stricter because it measures every click, tap and key press during a visit instead of only the first one. Any report or plugin still grading FID is using an outdated set of metrics.

A page passes when at least 75% of visits meet all three targets: Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less. These are separate thresholds, not a single number, so check each metric on both mobile and desktop.

The performance score out of 100 comes from a simulated Lighthouse test, while the Core Web Vitals assessment at the top of PageSpeed Insights uses real visitor data. They measure different things. Google assesses real-user data, so a passing field result matters more than a perfect lab score. Use the lab report to find causes, not as the goal.

Field data in the Chrome User Experience Report is a rolling 28-day average updated daily, so improvements appear gradually and take about four weeks to show fully. Search Console’s validation process can take a similar time. Lab tests in PageSpeed Insights show the effect of a change straight away, which helps confirm a fix worked.

Yes for visitors, though you may not see data. Pages need enough real Chrome visitors to appear in field reports, so small sites often show no data in Search Console. A slow or jumpy page still loses leads, so test your key pages with lab tools and fix what they find. Speed work also prepares the site for growth.

Yes. Heavy themes and page builders can add large amounts of CSS and JavaScript to every page, which slows loading and responsiveness. Caching and script delays help, but sometimes the theme itself is the limit. If scores stay poor after the basics, a lighter theme or a targeted Core Web Vitals fix is usually the next step.

The bottom line

Start by opening PageSpeed Insights on your most important page, on mobile, and note which of the three metrics fails. Then fix that metric on the whole template, give the field data four weeks to catch up, and move to the next template.

If your WordPress site keeps failing after the basics, our Core Web Vitals fixes task covers testing, fixes and a before-and-after report, and we are happy to talk it through first in a free consultation.

Sources

  1. Web Vitals, web.dev (Google), 2024-10-31
  2. Largest Contentful Paint (LCP), web.dev (Google), 2025-09-04
  3. Interaction to Next Paint (INP), web.dev (Google), 2025-09-02
  4. Cumulative Layout Shift (CLS), web.dev (Google), 2026-11
  5. Understanding page experience in Google Search results, Google Search Central, 2026-11
  6. Introducing INP to Core Web Vitals, Google Search Central Blog, 2023-05-10
  7. Performance chapter, Web Almanac 2025, HTTP Archive, 2026-01-15
  8. CrUX API, Chrome for Developers, 2026-11
  9. CrUX methodology, Chrome for Developers, 2026-11

Keep reading

Related guides

Dental SEO: How Patients Find a Dentist on Google and AI Search

SEO for dentists explained: how patients choose a dentist on Google Maps, search and AI tools, and what your practice needs to win more bookings.

Read the guide →

Ecommerce SEO Checklist for Shopify and WooCommerce Stores

An ecommerce SEO checklist for Shopify and WooCommerce: tracking, duplicate URLs, faceted navigation, product schema, page speed and category pages.

Read the guide →

How Much Does SEO Cost? Monthly Plans vs One-Off Tasks

How much does SEO cost in 2026? See monthly, hourly and project price ranges, when a one-off task beats a monthly plan, and how to check SEO is worth it.

Read the guide →

Get started

Want a second opinion on your scores?

Book a free consultation and we will look at your Core Web Vitals and tell you which fixes are worth doing first.