Core Web Vitals on WordPress: The Fixes That Matter (and the Ones That Don't)
Chasing a 100/100 score wastes money. Here's how to pass the actual field-data thresholds on a real WordPress site.
Muhammed Afsal
6 min read · 18 October 2026
Field data is the only score that counts
Lab scores fluctuate. Google ranks on 28-day real-user data (CrUX). Optimise for passing thresholds — LCP under 2.5s, INP under 200ms, CLS under 0.1 — not for a green screenshot.
LCP: usually one image
On most WordPress sites the LCP element is the hero image. Serve it in WebP/AVIF, size it correctly for mobile, preload it, and never lazy-load it. That single change fixes more sites than any caching plugin.
INP: your plugins are the problem
Heavy page-builder scripts and chat widgets delay every interaction. Audit with the Performance panel, delay non-critical JS, and remove plugins that load site-wide for one page's feature.
CLS: reserve space, always
Set width/height on images, reserve space for ads and embeds, and load webfonts with font-display: swap plus a sensible fallback stack.
What to ignore
Most 'opportunities' in PageSpeed Insights below the fold. Fix the template-level issues once and every page benefits.
Want this applied to your site?
Run the free instant audit, then book a call — I’ll walk you through exactly what to fix first.