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

Neeraj K Ravi Avatar
✨ Summarise and Analyse the Article

Core Web Vitals measure how fast, responsive, and visually stable a page feels for real users. In 2026, the three Core Web Vitals are Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS).

They matter for SEO because Google uses page experience signals, including Core Web Vitals, within its ranking systems. But they are not a shortcut to rankings. A page with excellent scores can still underperform if the content is weak, and a useful page can still rank even when its vitals need work.

For B2B SaaS websites, the practical goal is simple: make key pages fast enough to load, responsive enough to interact with, and stable enough that users can complete actions without friction.

Core Web Vitals 2026: the thresholds that matter

MetricWhat it measuresGood threshold
LCPHow quickly the main visible content loads2.5 seconds or less
INPHow quickly the page responds to user interactions200 milliseconds or less
CLSHow visually stable the page remains while loading0.1 or less

Google evaluates these thresholds using the 75th percentile of real-user visits. That means the experience should be good for at least 75% of visits, not just in a one-off lab test.

You can verify the thresholds in Google’s Core Web Vitals documentation and the web.dev Web Vitals guide.

Do Core Web Vitals affect SEO?

Yes, but not in the exaggerated way they are sometimes described.

Google includes Core Web Vitals within its broader page experience signals. Good performance can support a better user experience and can help when multiple pages are otherwise similarly useful. But Google explicitly says there is no single page experience signal that guarantees top rankings.

That means Core Web Vitals should be treated as part of technical SEO, not as a replacement for search intent, content quality, internal linking, authority, and crawlability.

LCP: fix slow main-content loading

Largest Contentful Paint measures how long it takes for the largest visible content element in the viewport to render. On many marketing sites, that is the hero image, hero text block, or another prominent above-the-fold element.

A good LCP is 2.5 seconds or less.

Common causes of poor LCP

  • Slow server response or weak hosting.
  • Large hero images or videos.
  • Render-blocking CSS or JavaScript.
  • Fonts that delay visible text.
  • Important content loaded too late in the page lifecycle.

How to improve LCP

  • Compress and properly size above-the-fold images.
  • Use modern image formats where appropriate.
  • Preload the LCP image when it is predictable and important.
  • Reduce unnecessary render-blocking scripts and styles.
  • Improve server response time and caching.
  • Avoid lazy-loading the primary hero image if it is the LCP element.

If a high-traffic landing page is consistently slow, include it in a broader website audit rather than fixing only the visual symptom.

INP: fix slow interactions

Interaction to Next Paint replaced First Input Delay as a Core Web Vital. INP measures the latency of user interactions across the page and reflects how quickly the browser can respond visually after a click, tap, or keyboard interaction.

A good INP is 200 milliseconds or less.

Common causes of poor INP

  • Long JavaScript tasks blocking the main thread.
  • Heavy third-party scripts.
  • Complex event handlers.
  • Large DOM updates triggered by interactions.
  • Interactive widgets that do too much work before the page can repaint.

For B2B SaaS websites, pay particular attention to pricing toggles, calculators, chat widgets, form embeds, cookie tools, menus, filters, and booking widgets. These are often conversion-critical and can also be the source of responsiveness problems.

How to improve INP

  • Break long JavaScript work into smaller tasks.
  • Remove or delay third-party scripts that are not needed immediately.
  • Reduce unnecessary JavaScript on marketing pages.
  • Keep event handlers lightweight.
  • Test important interactions on real pages, not only the homepage.

CLS: fix unexpected layout movement

Cumulative Layout Shift measures unexpected visual movement while a page is open. A good CLS is 0.1 or less.

CLS is a usability problem more than an abstract SEO metric. If a CTA moves just as someone is about to click it, or text jumps because a late-loading element appears above it, the page feels unreliable.

Common causes of poor CLS

  • Images or video embeds without reserved dimensions.
  • Late-loading cookie banners or promotional bars.
  • Forms and widgets injected above existing content.
  • Web fonts that change layout when they load.
  • Ads or dynamic blocks without reserved space.

How to improve CLS

  • Set width and height attributes or aspect ratios for media.
  • Reserve space for embeds, forms, ads, and widgets.
  • Avoid inserting banners above existing content after the page begins rendering.
  • Use font-loading strategies that minimise visible reflow.

Chrome has also expanded the performance data available through the Chrome User Experience Report. If your site uses heavy advertising or dynamic monetisation, our CrUX ad metrics explainer covers additional signals worth watching.

Field data vs Lighthouse: which should you trust?

Use both, but understand what each one is telling you.

Data typeWhat it showsBest use
Field dataPerformance from real Chrome users over timeUnderstanding whether users actually pass Core Web Vitals
Lab dataA controlled synthetic test of one page loadDiagnosing likely causes and testing fixes

PageSpeed Insights combines both when field data is available. The Core Web Vitals assessment is based on field data from the Chrome User Experience Report, while Lighthouse provides lab diagnostics that help explain what to fix.

A Lighthouse score of 95 does not mean every real visitor is getting a good experience. Likewise, a weak lab test does not automatically mean the URL fails field Core Web Vitals. Use the two datasets together.

How to check Core Web Vitals

For most SEO teams, three tools are enough to diagnose the majority of issues.

  1. PageSpeed Insights: Check individual URLs and compare field data with Lighthouse diagnostics.
  2. Google Search Console: Use the Core Web Vitals report to find groups of URLs with similar field-data problems.
  3. Chrome DevTools and Lighthouse: Investigate specific rendering, JavaScript, image, and main-thread issues.

Do not test only the homepage. Prioritise high-value templates and URLs such as service pages, pricing pages, demo pages, high-traffic articles, and landing pages. That is also how we recommend approaching a broader SEO audit.

Mobile vs desktop Core Web Vitals

You should monitor both mobile and desktop. Core Web Vitals are reported separately by device type because the experience can be very different.

Do not assume desktop matters more simply because B2B buyers often research on larger screens. Google uses mobile-first indexing, and mobile performance remains important for crawling, usability, and search. At the same time, desktop field data matters because real desktop users still need a fast and stable experience.

The right approach is not “mobile or desktop.” It is to fix whichever device group is failing on the URLs that matter to your business.

Do Core Web Vitals affect AI Overviews and AI search?

There is no separate Google Core Web Vitals threshold for AI Overviews or AI Mode, and Google has not published an official “Time to Cite” metric.

Google’s guidance for AI search is to follow the same core SEO fundamentals used for traditional search: make content accessible, crawlable, useful, well structured, and easy for users to navigate. Fast pages help because they improve the overall experience, but a Core Web Vitals pass is not a guarantee of inclusion in an AI answer.

If AI visibility is the goal, combine technical performance with clear entity information, strong internal linking, useful first-party content, and pages that directly answer the questions buyers ask. Our AI search SEO guide covers that wider strategy.

Core Web Vitals checklist for B2B SaaS websites

  • Check LCP, INP, and CLS using field data where available.
  • Prioritise revenue pages before low-value URLs.
  • Compress hero media and avoid unnecessary autoplay video.
  • Remove or delay third-party scripts that do not need to load immediately.
  • Audit chat, analytics, CRM forms, cookie tools, and marketing scripts for main-thread impact.
  • Reserve layout space for embeds, forms, banners, and dynamic components.
  • Test both mobile and desktop.
  • Recheck field data after deployment instead of relying only on a same-day Lighthouse score.

If your site has widespread technical issues across templates, JavaScript, indexing, and performance, a targeted Core Web Vitals fix may not be enough. That is where a full SEO audit and technical SEO program becomes more useful.

Frequently asked questions

What are the three Core Web Vitals in 2026?

The three Core Web Vitals are Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). Google considers LCP good at 2.5 seconds or less, INP good at 200 milliseconds or less, and CLS good at 0.1 or less, measured at the 75th percentile of real-user visits.

Do Core Web Vitals affect Google rankings?

Yes. Google uses Core Web Vitals as part of its broader page experience signals, but good scores do not guarantee high rankings. Search intent, content quality, authority, crawlability, internal linking, and other signals still matter.

Is INP more important than LCP or CLS?

No single Core Web Vital should be treated as the only important metric. INP measures responsiveness, LCP measures loading performance, and CLS measures visual stability. A page can create a poor experience by failing any one of them, so all three should be monitored.

Should I use PageSpeed Insights or Lighthouse for Core Web Vitals?

Use both. PageSpeed Insights can show Chrome User Experience Report field data when enough real-user data exists, while Lighthouse provides lab diagnostics for a controlled page load. Field data tells you what real users experience; Lighthouse helps identify what to fix.

Do Core Web Vitals affect AI Overviews?

Google has not published a separate Core Web Vitals requirement for AI Overviews or AI Mode. The same SEO fundamentals apply, including accessible content, crawlability, useful information, good page experience, and clear site structure. Passing Core Web Vitals alone does not guarantee inclusion in AI-generated search results.

Core Web Vitals are a technical foundation, not the whole SEO strategy

Core Web Vitals matter because slow, unresponsive, and unstable pages create friction for users. Fix them, but do not treat a green PageSpeed score as the finish line.

The strongest SEO pages combine useful content, solid technical foundations, clear internal linking, and a fast experience. If you want to identify where your site is losing performance across technical SEO, content, and page experience, start with our SEO audit checklist or explore OneMetrik’s SEO services.