Core Web Vitals in 2026: How Page Speed and INP Affect Your Google Rankings

Google’s Core Web Vitals have evolved from a nice-to-have technical checkbox into a genuine ranking differentiator — especially for competitive UK search terms. In 2026, with Interaction to Next Paint (INP) now fully replacing First Input Delay (FID) and Google tightening its page experience thresholds, the performance gap between fast sites and slow ones is widening in the SERPs.

If your website takes more than 2.5 seconds to load its largest content element, or if button clicks feel sluggish and unresponsive, you’re not just frustrating visitors — you’re actively losing rankings. Here’s what’s changed, what matters most, and how to fix it.

What Are Core Web Vitals in 2026?

Core Web Vitals are a set of three specific metrics that Google uses to measure real-world user experience on your website. They focus on loading performance, visual stability, and interactivity. Google introduced them as a ranking signal in 2021, and they’ve become progressively more influential each year since.

The three metrics in 2026 are:

These metrics are measured using real user data from the Chrome User Experience Report (CrUX), not synthetic lab tests. That means Google judges your site based on how actual visitors experience it — on their devices, their connections, in their locations.

Why Did Google Replace FID with INP?

First Input Delay (FID) only measured the delay before the browser could begin processing the first interaction on a page. The problem? Most pages had acceptable FID scores because the first click usually happens after the page has mostly loaded. FID told you nothing about what happened on the second, third, or tenth interaction.

INP measures every interaction throughout the entire page session — clicks, taps, key presses — and reports the worst-case responsiveness (specifically, the 98th percentile interaction). This means:

• A page that loads fine but becomes sluggish when users interact with dropdown menus, filters, or forms will fail INP
• Heavy JavaScript that blocks the main thread during scrolling or navigation will tank your score
• Third-party scripts (analytics, chat widgets, ad trackers) that fire during user interactions now directly impact your ranking signal

In practice, INP is much harder to pass than FID was. When Google made the switch in March 2024, the percentage of sites with “good” responsiveness scores dropped from 93% to approximately 65% overnight. Many sites that thought their performance was fine suddenly had a problem.

How Much Do Core Web Vitals Actually Affect Rankings?

This is the question every business owner asks, and the honest answer is: it depends on your competitive landscape. Core Web Vitals are not the most powerful ranking factor — content relevance, backlinks, and E-E-A-T signals still carry more weight individually. However, CWV act as a tiebreaker and amplifier.

Here’s what the data shows in 2026:

• Searchmetrics analysis of 2 million UK search results found that sites passing all three CWV metrics ranked an average of 3.2 positions higher than comparable sites that failed one or more metrics
• The effect is strongest in competitive niches — for queries where the top 10 results have similar content quality, page speed becomes a decisive differentiator
• Local search is particularly affected — Google’s local pack algorithm weighs page experience more heavily than standard organic results
• Sites that improved from “poor” to “good” CWV scores saw an average 12% increase in organic traffic within 60 days

The Conversion Impact

Rankings aside, Core Web Vitals directly affect your bottom line. Slow, janky websites lose customers — it’s that simple. Research from Deloitte found that:

• A 0.1-second improvement in mobile site speed increased conversion rates by 8.4% for retail sites and 10.1% for travel sites
• Pages loading in under 2 seconds had bounce rates 32% lower than pages loading in 5+ seconds
• Every additional second of load time reduces customer satisfaction by 16%

When we work on web design projects, Core Web Vitals optimisation is built into the development process from day one — not bolted on as an afterthought.

How to Check Your Core Web Vitals Scores

Before you can fix performance issues, you need to know where you stand. Here are the best tools for measuring Core Web Vitals:

1. Google Search Console — the Core Web Vitals report shows real-user data (CrUX) for your entire site, grouped by “Good”, “Needs Improvement”, and “Poor” URLs
2. PageSpeed Insights — provides both field data (real users) and lab data (simulated) for individual URLs, plus specific recommendations
3. Chrome DevTools — the Performance panel lets you profile interactions in real time, essential for debugging INP issues
4. Web Vitals Chrome Extension — shows real-time CWV scores as you browse your own site
5. CrUX Dashboard (Looker Studio) — tracks your CWV trends over time with historical data

We recommend checking Search Console monthly and running PageSpeed Insights tests after any significant site update (new plugins, theme changes, content additions).

How to Fix LCP (Largest Contentful Paint) Issues

LCP measures how long it takes for the largest visible content element — usually a hero image, featured image, or large text block — to render on screen. If your LCP exceeds 2.5 seconds, here’s how to fix it:

Image Optimisation

• Serve images in next-gen formats — WebP and AVIF are 25-50% smaller than JPEG/PNG with no visible quality loss
• Implement responsive images — use srcset and sizes attributes so mobile users don’t download desktop-sized images
• Lazy-load below-the-fold images — but never lazy-load the LCP element itself (this is a common mistake that actually worsens your score)
• Preload the LCP image — add <link rel="preload"> for your hero image so the browser fetches it immediately

Server and Hosting

• Time to First Byte (TTFB) under 800ms — if your server response is slow, everything else is slow. Consider upgrading hosting or implementing full-page caching
• Use a CDN — serve assets from edge locations closest to your users (Cloudflare is free and effective for UK businesses)
• Enable HTTP/2 or HTTP/3 — allows parallel downloading of assets, significantly reducing load times

Render-Blocking Resources

• Inline critical CSS — extract the CSS needed for above-the-fold content and inline it in the <head>
• Defer non-critical JavaScript — use async or defer attributes on scripts that don’t affect initial rendering
• Minimise CSS and JS file sizes — minification and compression can reduce file sizes by 60-80%

How to Fix INP (Interaction to Next Paint) Issues

INP is where most sites struggle in 2026. Fixing it requires understanding what happens on the browser’s main thread during user interactions. Here are the key strategies:

Reduce Main Thread Blocking

The main thread handles user interactions, JavaScript execution, and rendering. When heavy scripts monopolise the main thread, interactions queue up and feel sluggish.

• Break up long JavaScript tasks — any task over 50ms is considered “long”. Use requestAnimationFrame, setTimeout, or the newer scheduler.yield() API to split heavy work into smaller chunks
• Audit third-party scripts — analytics, chat widgets, retargeting pixels, and social embeds are notorious main-thread hogs. Remove anything you’re not actively using
• Delay non-essential scripts — load third-party scripts on user interaction (first scroll, first click) rather than on page load

Optimise Event Handlers

• Debounce scroll and resize handlers — don’t fire expensive functions on every pixel of scroll
• Use passive event listeners — add {passive: true} to scroll and touch listeners so they don’t block rendering
• Minimise DOM size — pages with more than 1,500 DOM nodes see significantly worse INP scores. Simplify your page structure

Common INP Culprits

How to Fix CLS (Cumulative Layout Shift) Issues

CLS measures unexpected layout shifts — when elements on the page move around as it loads. It’s the metric that makes users accidentally click the wrong thing because a button shifted just as they were about to tap it.

• Set explicit dimensions on images and videos — always include width and height attributes (or use CSS aspect-ratio) so the browser reserves the correct space before the asset loads
• Reserve space for ads and embeds — use min-height on containers that will hold dynamically loaded content
• Avoid inserting content above existing content — banners, cookie notices, and notification bars that push content down cause significant CLS
• Use font-display: swap with size-adjusted fallbacks — web fonts that load late cause text to reflow. Size-adjusted fallbacks minimise the shift
• Avoid dynamically injected content — if you must inject elements, use CSS transforms or content-visibility to avoid layout shifts

Core Web Vitals for WordPress Sites

WordPress powers over 40% of UK business websites, and it comes with specific CWV challenges. Here’s a WordPress-specific optimisation checklist:

1. Choose a performance-focused theme — avoid bloated multipurpose themes. Lightweight options like GeneratePress, Kadence, or custom-built themes score dramatically better
2. Limit active plugins to under 20 — each plugin adds JavaScript and CSS. Audit quarterly and remove anything redundant
3. Use a proper caching plugin — WP Rocket, W3 Total Cache, or LiteSpeed Cache (for LiteSpeed servers) can improve LCP by 40-60%
4. Implement an image optimisation plugin — ShortPixel, Imagify, or Smush for automatic WebP conversion and compression
5. Defer WooCommerce scripts on non-shop pages — WooCommerce loads cart and checkout scripts everywhere by default. Limit them to relevant pages only
6. Use a DNS-level CDN — Cloudflare’s free tier provides global CDN, HTTP/3, and automatic asset optimisation

For businesses that need their website rebuilt with performance as a priority, our SEO team works alongside design to ensure every site we deliver passes Core Web Vitals from launch day.

Related reading: Explore our guides on e-e-a-t 2026 and how to rank higher in google maps for more actionable insights.