Back to blog

Core Web Vitals: LCP, INP, CLS and How to Improve Them

SEO Course

Core Web Vitals: LCP, INP, CLS and How to Improve Them

By Forsa | SEO Audit and Technical SEO Specialist

What Core Web Vitals are, Google's thresholds for LCP, INP and CLS, how they affect rankings, how to test them and fixes for speed, mobile and HTTPS issues.

Updated 31 October 2026 · Part of the SEO guide series

Short answer: Core Web Vitals are three Google metrics for real-user experience: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness and Cumulative Layout Shift (CLS) for visual stability. Google's "good" targets are LCP within 2.5 seconds, INP under 200 milliseconds and CLS under 0.1, measured at the 75th percentile of visits. Google's ranking systems use Core Web Vitals, but good scores alone do not guarantee top rankings; they are one part of page experience alongside mobile-friendliness, HTTPS and avoiding intrusive pop-ups.

The three Core Web Vitals

Metric Measures Good Common causes of poor scores
LCP (Largest Contentful Paint) When the main content (largest image or text block) appears ≤ 2.5 s Slow server, large images, render-blocking CSS/JS, client-side rendering
INP (Interaction to Next Paint) How quickly the page responds to taps, clicks and key presses < 200 ms Heavy JavaScript, long tasks, third-party scripts
CLS (Cumulative Layout Shift) How much content moves unexpectedly while loading < 0.1 Images or ads without size, late-loading fonts, injected banners

INP replaced First Input Delay (FID) as the responsiveness metric because it covers all interactions during a visit, not just the first.

The 75th percentile rule: a page passes when at least 75% of visits meet the target, measured separately for mobile and desktop.

How much do Core Web Vitals affect rankings?

Google says Core Web Vitals are used by its ranking systems and recommends achieving good scores. It also says:

  • There is no single "page experience signal"; ranking systems look at a variety of signals.
  • Good results in Search Console or third-party tools do not guarantee your pages will rank at the top.

In practice, relevant, helpful content comes first. Page experience can make the difference between similar pages, and it always affects whether visitors stay and convert.

Field data vs lab data

  • Field data (real users, from the Chrome UX Report) is what Google uses. You see it in Search Console's Core Web Vitals report and the top of PageSpeed Insights.
  • Lab data (Lighthouse, a simulated test) helps you debug, but a good lab score does not mean real users have a good experience.

If you have no field data, the site may not have enough traffic yet; use lab tests and fix obvious problems.

How to check Core Web Vitals

  1. Search Console → Core Web Vitals report: groups of URLs marked Good, Needs improvement or Poor, for mobile and desktop.
  2. PageSpeed Insights: field data for a URL or origin, plus lab diagnostics and suggestions.
  3. Chrome DevTools / Lighthouse: detailed debugging during development.

Run a Quick Check on Any Page

Start with a fast overview before you dig into field data. A free SEO audit reports a page's load time, mobile friendliness and common on-page problems in 1 report, which helps you decide whether to look at images, scripts or the server first. Then confirm with PageSpeed Insights for field data, since real-user results are what Google uses.

Example: Fixing a Slow Product Page

An online store sees its product pages marked Poor for LCP on mobile in Search Console (illustrative case):

  1. Finding: the LCP element is a 2 MB hero photo, lazy-loaded by the theme, and the server takes over 1 second to respond.
  2. Changes: compress the image to a modern format at display size, remove lazy-loading for that first image, add fetchpriority="high" and turn on page caching.
  3. Result to measure: LCP in lab tests drops quickly, but the Search Console report updates only as new field data arrives over about 28 days.

The fix was made once in the product template, so it applied to every product page. That is why starting with templates pays off.

How to fix LCP

  • Speed up the server response (caching, a CDN, efficient hosting).
  • Make the LCP element (often the hero image) load early: do not lazy-load it, consider fetchpriority="high", and serve it in a modern format at the right size.
  • Remove or defer render-blocking CSS and JavaScript.
  • For JavaScript-heavy sites, serve the main content in the initial HTML (server-side rendering or prerendering).

How to fix INP

  • Break up long JavaScript tasks and remove unused code.
  • Reduce or delay third-party scripts (chat widgets, tag managers, ads).
  • Keep event handlers light; show visual feedback immediately, then do heavy work.
  • Avoid large layout updates after each interaction.

How to fix CLS

  • Set width and height (or aspect ratio) on images, videos, embeds and ad slots.
  • Reserve space for banners and cookie notices instead of pushing content down.
  • Use font-display options and preload key fonts to reduce text shifts.
  • Do not insert content above existing content unless the user asked for it.

Mobile: mobile-first indexing

Google uses the mobile version of your pages, crawled with its smartphone crawler, for indexing and ranking. To avoid losing content or rankings:

  • Keep the mobile content equivalent to desktop (you can use tabs or accordions, but the content must be there).
  • Use the same headings, structured data and metadata on mobile.
  • Do not lazy-load primary content only after a tap, swipe or typing; Google won't trigger those interactions.
  • Let Google crawl the resources (CSS, JS, images) needed to render the page.

Check mobile usability with Lighthouse in Chrome, which Google lists among its page experience resources, and by testing on real phones.

Security: HTTPS

Serve every page over HTTPS with a valid certificate, redirect HTTP to HTTPS, and fix mixed content (HTTP images or scripts on HTTPS pages). Search Console's HTTPS report shows pages that are not served securely.

The rest of page experience

Google suggests asking:

  • Do your pages have good Core Web Vitals?
  • Are they served securely?
  • Does content display well on mobile?
  • Do you avoid excessive ads that distract from the main content?
  • Do you avoid intrusive interstitials?
  • Can visitors easily find the main content?

Where to start

  1. Fix pages marked Poor in Search Console, starting with templates that cover many URLs (one fix helps all of them).
  2. Fix LCP on key landing pages, then CLS, then INP.
  3. Confirm mobile content parity and HTTPS everywhere.
  4. Re-check field data after about 28 days, since the Chrome UX Report uses a rolling 28-day window.

For how these fit into crawling, indexing and site structure, see technical SEO foundations. For paid landing pages, see PPC landing page optimization.

FAQs

What are Core Web Vitals?

Three Google metrics for real-user page experience: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability).

What are good Core Web Vitals scores?

LCP within 2.5 seconds, INP under 200 milliseconds and CLS under 0.1, for at least 75% of visits on mobile and desktop.

Are Core Web Vitals a ranking factor?

Yes, Google says its ranking systems use them. But there is no single page experience signal, and good scores do not guarantee top rankings; content relevance and quality matter more.

Do Core Web Vitals Matter for Small Sites With Little Traffic?

They still affect real visitors, so slow or unstable pages are worth fixing. A small site may have too little traffic for field data to appear, so use lab tests to find and fix clear problems, and look for field data later.

How Long Until Search Console Shows an Improvement?

Field data uses a rolling 28-day window, so a fix usually shows up gradually over about a month. Use lab tests to confirm a fix works right away, then wait for field data to confirm it for real users.

Why is my PageSpeed Insights score good but Core Web Vitals fail?

The score is lab data from a simulated test. Core Web Vitals assessment uses field data from real users, who may have slower devices and networks. Fix what real users experience.