Core Web Vitals are now part of how Google ranks your site. The metrics are not arbitrary — they correlate with whether real users feel the site is fast and responsive. The bad news: WordPress out of the box rarely passes them. The good news: the fixes are well understood.
There are three metrics that matter, and each fails for different reasons.
LCP — Largest Contentful Paint
LCP measures how long until the largest visible element on your page (usually a hero image or hero text) finishes loading. Google wants this under 2.5 seconds.
The most common WordPress LCP problems:
- The hero image is not optimized. If your hero is a 1200KB JPEG, no amount of caching will make LCP green. Compress aggressively, serve as WebP, and add
fetchpriority="high"on the<img>tag. - Render-blocking CSS. Your stylesheet has to download and parse before the browser can paint. Inline critical CSS (the styles needed for the visible part of the page) and async-load the rest.
- Slow Time to First Byte. If your hosting takes 800ms to send the first byte, you have already lost a third of your LCP budget. See the previous post on hosting.
INP — Interaction to Next Paint
INP replaced FID in 2024. It measures how responsive your page feels to clicks and taps. Google wants this under 200 milliseconds.
WordPress sites usually fail INP for two reasons:
- Heavy third-party scripts on the main thread. Chat widgets, analytics, ad scripts, A/B testing tools — they all run JavaScript that blocks the page from responding to clicks. Defer everything you can. Lazy-load chat widgets to load only after first interaction.
- Bloated themes that do too much on every event. Some page builders attach JavaScript event handlers to every element on the page. Click anywhere and the browser stalls. The fix is usually a leaner theme or a page-builder configured to skip features you do not use.
CLS — Cumulative Layout Shift
CLS measures how much things move around as the page loads. If you have ever clicked a button and it jumped away because an ad loaded above it — that is layout shift. Google wants CLS under 0.1.
WordPress-specific CLS causes:
- Images without dimensions. If your
<img>tags do not have explicit width and height attributes, the browser does not know how much space to reserve. The image loads, the page jumps. Modern WordPress emits dimensions automatically; older themes sometimes strip them. - Web fonts loading late. When a custom font swaps in over the system fallback, text reflows. Use
font-display: optionalor preload the font. - Cookie banners and announcement bars. If they push content down on load, that is layout shift. Reserve their space at render time, do not insert them as a top-of-page surprise.
How to actually measure
Two tools, used together:
- PageSpeed Insights for synthetic benchmarks. Tells you what is wrong.
- Search Console > Core Web Vitals report for real-user data. Tells you whether real visitors actually experience what PageSpeed predicts. The numbers can differ — real users have slower devices and worse connections than the lab.
Aim to pass on real-user data. Lab scores in the 90s with real-user scores in the 60s usually means your hosting is fine but a chunk of your audience is on slow connections you have not optimized for.
The 80/20
If you do exactly three things, most WordPress sites pass Core Web Vitals: optimize the hero image, defer non-critical JS, and reserve dimensions on every image. Everything else is polish.