Core Web Vitals 2026: What Changed and What You Must Fix

Core Web Vitals have been a Google ranking factor since May 2021. In March 2024, Google made the most significant update to the metrics since their launch: replacing First Input Delay (FID) with Interaction to Next Paint (INP).

If you haven't audited since early 2024, you may be failing the updated standard without knowing it.

If you haven't audited your Core Web Vitals performance since early 2024, you may be failing the updated standard without knowing it — because the new INP metric is significantly harder to pass than FID was.

The Three Core Web Vitals in 2026

LCP
Largest Contentful Paint

What it measures: How long it takes for the largest visible content element on the page to fully render — typically a hero image, a large text block, or a video thumbnail.

Why it matters: LCP represents the point at which users perceive the page as "loaded." Slow LCP = users see a blank or partially loaded page for too long = poor experience.

Target scores:

Status Threshold
🟢 Good2.5 seconds or faster
🟡 Needs Improvement2.5–4.0 seconds
🔴 PoorOver 4.0 seconds
Ranking impact: LCP is weighted most heavily among the three Core Web Vitals. It has the highest correlation to user satisfaction and most directly influences "page experience" ranking signals.
INP
Interaction to Next Paint NEW IN 2024

What it measures: The delay between a user interacting with the page (clicking a button, tapping a link, pressing a key) and the browser painting the next visual response. INP measures the worst interaction across an entire page visit.

Why it matters: INP replaces FID (First Input Delay), which only measured the very first interaction. INP measures all interactions throughout a visit — capturing the sluggishness of complex pages with many JavaScript-heavy interactions.

Target scores:

Status Threshold
🟢 Good200 milliseconds or faster
🟡 Needs Improvement200–500 ms
🔴 PoorOver 500 ms
Why INP is harder than FID: (1) It measures every interaction, not just the first one. (2) JavaScript-heavy pages often fail INP even if FID was green. (3) The measurement period is longer (entire session vs. first interaction). Many sites with all-green Core Web Vitals under FID now have poor INP scores — particularly sites using page builders (Elementor, Divi), complex JavaScript frameworks, or heavy third-party scripts.
CLS
Cumulative Layout Shift

What it measures: The visual stability of the page — how much content unexpectedly shifts position while the page loads. A page that "jumps" as images load or ads appear has high CLS.

Why it matters: Layout shifts cause users to click the wrong button, lose their reading position, or accidentally tap unintended links. High CLS correlates strongly with user frustration.

Target scores:

Status Threshold
🟢 Good0.1 or lower
🟡 Needs Improvement0.1–0.25
🔴 PoorOver 0.25

Common CLS causes: Images without defined dimensions, dynamically injected ads, fonts loading late (FOUT/FOIT), third-party embeds without reserved space.

How Core Web Vitals Affect Rankings

Google uses Core Web Vitals as a tie-breaker ranking signal within the broader "page experience" signal. The official position: two pages with equal content quality and authority will have the better-performing page ranked higher.

In practice, the impact is subtle for most queries but meaningful in competitive niches. Passing all three Core Web Vitals earns a "page experience" signal that failing sites don't receive.

More significantly for 2026: Google AI Overviews and featured snippet selection also considers page experience. A slow, poor-experience page is less likely to be cited or featured — even with excellent content.

The practical priority: Core Web Vitals are a quality gate. Failing them doesn't destroy rankings, but passing them removes a disadvantage and improves both traditional rankings and AI feature eligibility.

How to Measure Your Core Web Vitals

01
Google Search Console (Most Important)

Search Console's Core Web Vitals report shows your real-user data (CrUX — Chrome User Experience Report data collected from real Chrome users visiting your site).

Access: Search Console → Core Web Vitals → Mobile/Desktop

Pages categorised as "Poor" are the priority to fix. "Needs Improvement" is the next priority. "Good" means you're passing.

Minimum threshold: To earn the page experience signal for a URL, that URL must be in the "Good" category for all three metrics.
02
PageSpeed Insights

Visit pagespeed.web.dev → Enter any URL → Run the test.

PageSpeed Insights shows both:

  • Field data: Real-user CrUX data for that URL (same as Search Console)
  • Lab data: A simulated test result from your current page state

The field data is what matters for rankings. Lab data is useful for diagnosing the cause of poor field data.

03
Chrome DevTools Performance Tab

For deep diagnosis — identifying exactly which JavaScript functions are causing INP issues, which elements are causing layout shifts — Chrome DevTools provides performance traces that point to the exact code causing problems.

Fixing LCP: Step-by-Step

Poor LCP is almost always caused by one or more of these factors:

01
Optimise the LCP Image

The LCP element is usually your hero image. If it's large and unoptimised:

  • Compress the image: Use WebP format (30–35% smaller than JPEG). ShortPixel, Imagify, or Squoosh handle this
  • Resize to display dimensions: A 4000px image displayed at 1200px wastes bandwidth. Serve the size actually displayed
  • Add fetchpriority="high": Tell the browser this image is the most important element to load
HTML
<img src="hero.webp" fetchpriority="high" alt="Hero image">

Preload the LCP image in <head>:

HTML
<link rel="preload" as="image" href="/images/hero.webp">
02
Eliminate Render-Blocking Resources

CSS and JavaScript that block the browser from rendering HTML delay LCP. Diagnose with PageSpeed Insights' "Render-blocking resources" opportunity.

  • Defer non-critical JavaScript: <script defer src="..."> or <script async src="...">
  • Move non-critical CSS to load asynchronously
  • Use WP Rocket or LiteSpeed Cache's built-in render-blocking elimination features
03
Upgrade to Better Hosting

LCP is heavily influenced by Time to First Byte (TTFB) — how long the server takes to respond. Cheap shared hosting with poor TTFB directly causes LCP failures.

If TTFB is above 800ms, hosting upgrade is the most direct LCP fix. Cloudways, Kinsta, or SiteGround Business improve TTFB significantly.
04
Enable Caching and CDN
  • Caching plugin (WP Rocket, LiteSpeed Cache)
  • CDN (Cloudflare) for serving assets from nodes near users
These two alone can improve LCP by 30–50% on poorly optimised sites.

Fixing INP: Step-by-Step

INP is the hardest metric to fix because it requires addressing JavaScript execution delays.

01
Identify the Failing Interactions

In Chrome DevTools:

  1. Open the page
  2. Press F12 → Performance tab
  3. Click "Start profiling and reload page"
  4. Interact with elements (click buttons, fill forms, navigate menus)
  5. Stop recording
  6. Look for "Long Tasks" (red bars) in the main thread — these are interactions causing INP failures
02
Reduce JavaScript Execution Time

The most common INP failure cause: too much JavaScript running on user interactions.

  • Disable unused plugin scripts: Use Asset CleanUp or Perfmatters to prevent plugins from loading JS on pages where they're not needed
  • Defer third-party scripts: Analytics, chat widgets, and ad scripts often delay interactions
  • Replace heavy page builders: Elementor and Divi are significant INP contributors on complex pages. Consider migrating to lighter Gutenberg blocks
03
Minimise Third-Party Script Impact

Third-party scripts (Google Analytics, Facebook Pixel, HubSpot chat, Intercom) execute in the main thread and contribute to INP.

  • Load them with async or defer
  • Use Google Tag Manager to consolidate and control script loading
  • Consider delaying non-critical scripts until after the page is interactive (WP Rocket's "delay JavaScript" feature)

Fixing CLS: Step-by-Step

01
Set Image Dimensions

Every <img> tag should have explicit width and height attributes:

HTML
<img src="product.webp" width="600" height="400" alt="Product">

This tells the browser how much space to reserve before the image loads, preventing layout shift.

02
Reserve Space for Ads and Embeds

Dynamically loaded ads and embeds that don't have pre-reserved space cause CLS.

  • Set min-height on ad containers
  • Use aspect-ratio CSS for embeds
CSS
.video-container {
  aspect-ratio: 16 / 9;
  width: 100%;
}
03
Handle Font Loading

Web fonts that load after the page causes "Flash of Unstyled Text" (FOUT), which shifts layout.

  • Use font-display: swap in @font-face declarations
  • Preload key fonts
  • Self-host Google Fonts (eliminates external request latency)
HTML
<link rel="preload" as="font" href="/fonts/main.woff2" crossorigin>

Core Web Vitals by Platform

Platform LCP Impact INP Impact CLS Impact Notes
WordPress + WP Rocket Strong (caching, image lazy load) Moderate (JS optimisation) Strong (deferred JS) Best all-in-one option
WordPress + Elementor Moderate High risk (heavy JS) Moderate Consider Gutenberg for simpler pages
WordPress + LiteSpeed Cache Strong Strong Strong Best on LiteSpeed servers

Frequently Asked Questions

Q: Do Core Web Vitals directly affect my Google rankings?
A: Yes, as a tie-breaker within the Page Experience signal. The effect is most pronounced in competitive niches. For most sites, the bigger impact is on AI Overview citation eligibility and user experience metrics that correlate with conversions.
Q: My Core Web Vitals pass on desktop but fail on mobile. Which matters more?
A: Mobile. Google uses mobile-first indexing — mobile performance is the primary signal. Prioritise mobile Core Web Vitals fixes.
Q: INP is the new metric and my site is failing it. What's the fastest fix?
A: Start with Perfmatters or Asset CleanUp to identify and disable unnecessary JavaScript on specific pages. Then check for third-party script impact (analytics, chat). If using Elementor or Divi heavily, those builders' JS is likely a primary culprit.
Q: How often should I check Core Web Vitals?
A: Monthly at minimum. Search Console data rolls on a 28-day window, so check monthly to catch regressions early. After making fixes, wait 28 days for the new data to fully reflect before evaluating results.
Q: Can a good CDN alone fix my LCP issues?
A: A CDN helps significantly (especially for users far from your server) but rarely fixes LCP alone. If your TTFB is slow (server response time), the CDN can't make the initial response faster. Combine CDN with image optimisation, caching, and hosting quality for full LCP improvement.

Final Thoughts

Core Web Vitals are not going away — they're becoming more sophisticated. The shift from FID to INP is the clearest signal of this: Google is raising the bar for what constitutes a "good" user experience.

Passing Core Web Vitals is both a ranking prerequisite and a business improvement. Faster, more stable, more responsive pages convert better, rank better, and earn more AI feature citations.

Audit with Search Console first. Fix failing LCP with image optimisation and hosting. Address INP with JavaScript cleanup. Solve CLS with explicit image dimensions.

Contact us for a Core Web Vitals audit
Views: 59