Core Web Vitals in 2026: What They Are, Why They Matter and How to Fix Them
Google uses Core Web Vitals as a ranking signal. Most business websites fail at least one. Here's how to diagnose and fix every metric that matters.
What are Core Web Vitals?
Core Web Vitals (CWV) are three user experience metrics that Google uses as part of its page experience ranking signal. They measure how fast your page loads, how quickly it responds to user input, and how stable the layout is while loading. Since 2021, poor CWV scores directly suppress search rankings — the first time Google explicitly connected UX measurements to position.
The three metrics are: Largest Contentful Paint (LCP) — how long until the main content of the page is visible; Interaction to Next Paint (INP) — how responsive the page is to clicks and taps (replaced First Input Delay in March 2024); and Cumulative Layout Shift (CLS) — how much the page layout jumps around as it loads. Each has a Good, Needs Improvement and Poor threshold.
Google's PageSpeed Insights, Search Console's Core Web Vitals report and the Chrome User Experience Report (CrUX) all surface these metrics. The CrUX data is based on real Chrome users visiting your site — it's what Google actually uses for ranking, and it can differ significantly from lab scores in PageSpeed Insights.
The 2026 benchmarks you need to hit
LCP (Largest Contentful Paint): Good is under 2.5 seconds. Poor is over 4 seconds. LCP is typically triggered by your hero image or the largest text block above the fold. For most service business websites, a poorly optimised hero image is the single biggest LCP issue.
INP (Interaction to Next Paint): Good is under 200 milliseconds. Poor is over 500 milliseconds. INP measures the latency of your worst interaction during a page visit — a slow JavaScript event handler that fires on a button click, for example. This is the newest metric and the one most business websites are least prepared for.
CLS (Cumulative Layout Shift): Good is under 0.1. Poor is over 0.25. CLS is caused by elements that load asynchronously and push other content around — fonts loading after text, images without declared dimensions, ads injecting into the layout. Even small shifts are penalised cumulatively across the page session.
Find out how your website scores on Core Web Vitals
iGrowix runs a full technical SEO audit including CWV diagnosis and a prioritised fix plan. Free for qualifying businesses in the UK, Australia and USA.
Get a free CWV audit →Fixing LCP: the most common performance bottleneck
For most websites, fixing LCP means fixing your hero image. The solutions: serve the hero image in WebP or AVIF format (30–50% smaller than JPEG at equivalent quality); add `fetchpriority="high"` to the hero image tag to tell the browser to load it before other resources; preload it in the document `<head>` with `<link rel="preload" as="image">`; and ensure it's served from a CDN with a point of presence close to your users.
Server response time (Time to First Byte, TTFB) is the upstream cause of poor LCP. A slow server means everything downstream is delayed. UK businesses should target TTFB under 200ms; if yours is over 600ms, server infrastructure is the problem, not the page code. Consider upgrading hosting or switching to a managed hosting provider with better infrastructure.
Render-blocking resources — large CSS files and synchronous JavaScript in the `<head>` — delay LCP by preventing the browser from painting the page. Move non-critical scripts to load asynchronously or defer, and split CSS so only the above-the-fold styles are loaded inline on first render.
Fixing INP: the JavaScript performance problem
INP is directly tied to JavaScript execution on the main thread. If your page has large JS bundles that block the browser thread, any user interaction during script execution is delayed — sometimes by hundreds of milliseconds. The primary fix is reducing main-thread blocking time.
Audit your JavaScript with Chrome DevTools Performance panel. Look for Long Tasks (>50ms) and identify which scripts trigger them. Common culprits: bloated third-party scripts (chat widgets, analytics, cookie consent tools), heavy React or Vue re-renders triggered by user events, and synchronous DOM manipulation in event handlers.
Break up long tasks: use `setTimeout` or the Scheduler API to yield to the browser between non-critical work. Consider implementing code splitting so only the JavaScript needed for the current page loads initially. Third-party scripts — particularly chat widgets and A/B testing tools — are frequently the worst INP offenders and may need to be loaded conditionally or replaced with lighter alternatives.
Need technical SEO and performance help?
Our development team fixes CWV issues for business websites across the UK, Australia and USA — improving rankings and conversion rates simultaneously.
Explore our web design & SEO service →Fixing CLS: stopping your layout from jumping
Always declare explicit width and height attributes on images and video elements. Without them, the browser doesn't know how much space to reserve while the media loads, causing content below it to shift when the image appears. This single change fixes the majority of CLS issues on content-heavy pages.
Web fonts cause CLS when the fallback font and the loaded font have different metrics (line height, letter spacing). Fix this with `font-display: optional` (shows fallback only if web font loads instantly) or by using `size-adjust`, `ascent-override` and `descent-override` CSS properties to match the fallback font metrics to your web font as closely as possible.
Avoid inserting content above existing content dynamically. Cookie consent banners that push the page down, ads that inject above the fold, and promotional bars that load after the initial paint all generate CLS. Load them in reserved space or overlay them rather than displacing content.
Core Web Vitals and your search rankings: the real impact
Google uses CWV as a tiebreaker, not a primary ranking factor. A page with excellent CWV but thin content will not outrank a page with poor CWV but comprehensive, authoritative content. However, in competitive markets where multiple pages are similarly authoritative, CWV is the differentiator — and a meaningful one.
The more direct impact is on conversion rate, not ranking. Extensive research (Cloudflare, Google, Portent) consistently shows that pages loading in under 2 seconds convert at 2–3× the rate of pages loading in 5+ seconds. For an e-commerce store or service business generating enquiries, this is often worth far more than the marginal ranking improvement.
Monitor your CWV scores monthly in Google Search Console's Core Web Vitals report, which segments performance by device type and URL group. Focus on mobile scores — Google's mobile-first indexing means mobile CWV is the measurement that matters most for rankings, even if your traffic is majority desktop.
A faster website ranks better and converts better
iGrowix builds and optimises websites for Core Web Vitals performance — new builds and existing site improvements. Let's see what your site scores today.
Talk to our technical team →