In short: Core Web Vitals are Google’s page-experience metrics: Largest Contentful Paint (LCP – loading), Interaction to Next Paint (INP – interactivity) and Cumulative Layout Shift (CLS – visual stability). In 2026 they remain confirmed ranking signals and – more importantly – directly affect conversions and crawl efficiency. This guide explains each metric, how to measure them, and the exact fixes for WordPress sites.
Last updated: October 2026.
Google doesn’t just rank pages – it ranks experiences. Core Web Vitals quantify what “fast and stable” means: how quickly the main content appears, how fast the page responds to taps, and whether things jump around while loading. Pass all three and you remove a ranking handicap and a conversion handicap at once.
The three Core Web Vitals
Largest Contentful Paint (LCP) – target: under 2.5s. When the largest visible content element (usually the hero image or headline block) finishes rendering. Measures perceived loading speed.
Interaction to Next Paint (INP) – target: under 200ms. How quickly the page responds to user interactions (taps, clicks, key presses), measured across the whole visit. Replaced First Input Delay in 2024; it’s the stricter, more honest interactivity metric.
Cumulative Layout Shift (CLS) – target: under 0.1. How much visible content shifts unexpectedly during load. That maddening moment when text jumps just as you tap – that’s CLS, and Google penalises it.
Thresholds: “Good” (above), “Needs Improvement” (LCP 2.5-4s, INP 200-500ms, CLS 0.1-0.25), “Poor” (worse). Aim for Good on 75% of page views – that’s the bar Google uses.
How to measure Core Web Vitals
PageSpeed Insights. Enter any URL: lab data (instant) + field data (real Chrome users, 28-day rolling). Field data is what Google actually uses for ranking – lab data is for debugging.
Search Console → Core Web Vitals report. URL groups across your whole site: which templates fail, on mobile vs desktop. Start here for site-wide triage.
CrUX / Lighthouse. Chrome UX Report for competitor benchmarking; Lighthouse in DevTools for lab diagnostics during fixes.
Web Vitals Chrome extension. Real-time overlay while browsing – invaluable when auditing client sites.
Golden rule: fix what field data flags, verify with lab tools. Chasing perfect lab scores on pages with no traffic is theatre.
Fixing LCP (loading)
Optimise the hero image. It’s usually the LCP element: convert to WebP/AVIF, size it correctly (no 4000px images displayed at 800px), preload it, and never lazy-load above-the-fold images.
Server response time. TTFB is the floor LCP stands on: quality hosting, page caching (server-level or plugin), PHP 8+, database optimisation. A 1.5s TTFB makes sub-2.5s LCP nearly impossible.
Kill render-blocking resources. Defer non-critical JavaScript, inline critical CSS, delay third-party scripts (chat widgets, heatmaps) until after load. Audit with Lighthouse’s “render-blocking resources” list – it’s usually short and damning.
Fonts. Use font-display: swap, preload key font files, subset fonts to needed characters. Webfont delays are a top-5 LCP killer on content sites.
Fixing INP (interactivity)
Reduce JavaScript weight. INP suffers when the main thread is busy. Audit your JS bundle: remove unused plugins, defer everything non-critical, split vendor code. WordPress sites with 15+ plugins are the classic INP disaster.
Break up long tasks. Any JS task over 50ms blocks interaction. Defer heavy work, use web workers for computation, lazy-initialise below-fold components.
Event handler hygiene. Debounce scroll/resize handlers, avoid layout thrashing in handlers, keep handlers lean. A chat widget’s message polling can wreck INP site-wide.
Third-party audit. Tags, pixels, widgets – each adds main-thread work. If it’s not earning its place (measured conversions), remove it. Tag Manager makes this audit easy.
Fixing CLS (stability)
Reserve space for everything. Images and videos: width/height attributes or aspect-ratio CSS. Ads/embeds: fixed-size containers. Iframes: explicit dimensions. The browser can’t hold space for what it can’t measure.
No late injections above the fold. Cookie banners, promo bars, newsletter popups that push content down after load – reserve their space upfront or overlay them without shifting layout.
Fonts again. Font swaps change text metrics and shift layouts. Well-matched fallbacks minimise the jump.
Dynamic content. “Related posts” or ad slots loading late: skeleton placeholders with fixed dimensions. Users perceive skeletons as fast; layout jumps as broken.
WordPress-specific playbook
- Hosting first. Shared $5 hosting can’t deliver sub-2.5s LCP under load. Managed WordPress or a tuned VPS is the baseline.
- Caching: page cache + object cache (Redis). WP Super Cache / LiteSpeed Cache / WP Rocket – pick one, configure fully.
- Images: WebP conversion, correct sizing, lazy-load below fold only. A media optimisation plugin pays for itself.
- Plugin diet: audit quarterly. Each active plugin is JS/CSS/database weight. Deactivate, test, delete.
- Theme weight: multipurpose themes with 40 demos ship bloat you’ll never use. Lightweight themes (or well-built custom) win.
- CDN: Cloudflare (free tier) for static assets + DNS speed worldwide.
Core Web Vitals mistakes
- Chasing lab scores, ignoring field data. A 100 Lighthouse score with Poor field data means your test conditions don’t match reality.
- Fixing once. Every plugin install, theme update and new widget regresses vitals. Monitor monthly via Search Console.
- Desktop-only testing. Google ranks on mobile vitals. Test mobile first, always.
- Ignoring INP. The newest metric is the one most sites fail. It deserves equal attention to LCP.
- Speed plugins as magic. Caching plugins help, but they can’t fix bad hosting, 3MB hero images or 20 render-blocking scripts. Fix the causes.
Speed is a feature
Core Web Vitals sit at the intersection of technical SEO, CRO and user experience: rankings, conversions and satisfaction all move together. It’s rare, measurable, improvable work – the best kind.
At Vans Marketing, every technical audit includes a full vitals diagnosis with prioritised fixes. Get a free audit and see where your site stands.
Core Web Vitals – frequently asked questions
What are Core Web Vitals?
Core Web Vitals are Google’s three page-experience metrics: Largest Contentful Paint (loading speed, target under 2.5s), Interaction to Next Paint (interactivity, target under 200ms) and Cumulative Layout Shift (visual stability, target under 0.1). They’re confirmed Google ranking signals.
Are Core Web Vitals still important in 2026?
Yes. They remain ranking signals, and their business impact (conversions, bounce rates) is independent of SEO. INP, the newest metric, is where most sites currently fail – making it the highest-leverage fix.
What’s a good Core Web Vitals score?
Google’s bar: LCP under 2.5s, INP under 200ms, CLS under 0.1, achieved on 75% of real-user page views (field data). Lab-perfect scores don’t count if real users experience worse.
How do I check my site’s Core Web Vitals?
PageSpeed Insights for any single URL (lab + field data), Search Console’s Core Web Vitals report for site-wide mobile/desktop breakdowns, and Lighthouse in Chrome DevTools for debugging specific issues.
Can Core Web Vitals alone improve my rankings?
They remove a handicap rather than guaranteeing gains – but on competitive queries, the tiebreaker effect is real. Combined with their conversion impact, vitals work pays for itself many times over.