How to Improve Core Web Vitals in WordPress (LCP, INP and CLS)

Core Web Vitals are the three measurements Google uses to judge how a page feels to a real visitor: how fast the main content appears, how quickly the page responds when you interact with it, and how much the layout jumps around while loading. They’re a ranking signal, they show up in Search Console, and more importantly they mirror whether your site feels fast or frustrating.

This is a practical, WordPress-specific guide. No theory for theory’s sake: each section tells you what the metric means, what usually hurts it on a WordPress site, and what to do about it.

The three metrics in plain English

• LCP (Largest Contentful Paint): how long until the biggest visible element (usually your hero image or heading) is on screen. Good: under 2.5 seconds.
• INP (Interaction to Next Paint): how quickly the page reacts when someone taps, clicks or types. Good: under 200ms. INP replaced the older FID metric in 2024.
• CLS (Cumulative Layout Shift): how much the layout jumps around as things load. Good: under 0.1.

Measure first: lab data vs field data

Run your page through PageSpeed Insights. You’ll see two kinds of numbers: field data at the top (what real Chrome users experienced over the last 28 days) and lab data below (a one-off simulated test). Field data is what actually counts for Google, but a new or low-traffic site won’t have any yet, so lab data is your working proxy. Search Console’s Core Web Vitals report shows you which URLs need attention as field data accumulates.

Improving LCP: get the main thing on screen fast

Fix the foundations

LCP is mostly a delivery problem. Slow hosting, no caching and heavy pages delay everything, so if you haven’t already, start with the basics in my guide to why WordPress sites are slow. Page caching plus a CDN routinely takes seconds off LCP on its own.

Optimise the LCP element itself

• Serve the hero image as WebP, sized to what’s displayed, not a 4000px original
• Never lazy-load the LCP image. Lazy-loading above-the-fold images is one of the most common self-inflicted LCP wounds in WordPress
• Preload it: <link rel="preload" as="image"> tells the browser to fetch it immediately (LiteSpeed Cache and most performance plugins can do this)
• Prefer a real image or solid colour over full-screen background videos and sliders — sliders are LCP poison

Improving INP: stop making the browser think so hard

INP suffers when the browser’s main thread is busy running JavaScript instead of responding to your visitor. On WordPress the usual suspects are too many plugins loading scripts everywhere, heavy page-builder animations, and third-party embeds.

• Defer non-critical JavaScript (a caching plugin setting) so it loads after the page is usable
• Remove or replace plugins that load site-wide scripts for a feature used on one page
• Load analytics and chat widgets after interaction or with a delay
• Keep fancy scroll effects and animations for where they earn their keep — every effect is JavaScript the main thread has to run

Improving CLS: stop the page jumping around

Layout shift is the most fixable of the three. It happens when the browser doesn’t know how much space something needs until it arrives.

• Always set width and height (or aspect ratio) on images so the browser reserves space — WordPress does this automatically for properly inserted images
• Reserve space for embeds, ads and iframes with a min-height on their container
• Use font-display: swap and preload your main font so text doesn’t reflow when the font arrives
• Avoid injecting banners or notices above existing content after the page has loaded

Elementor-specific tips

Elementor sites can absolutely pass Core Web Vitals — this site is built with Elementor and scores 100/100 in lab tests. What matters: a clean container structure instead of deep nesting, global styles instead of styling every element individually, Elementor’s built-in “Optimized Markup” and font-display settings enabled, and restraint with widgets that ship their own libraries. A rebuild of a messy page is sometimes faster than optimising it.

Set realistic expectations

Two honest caveats. First, field data updates on a 28-day rolling window — fixes take weeks to show in Search Console, so don’t panic-revert after three days. Second, passing Core Web Vitals won’t rocket you up the rankings by itself; it removes a penalty and improves every visit, but content and relevance still do the heavy lifting. Anyone promising “guaranteed rankings” from speed work alone is overselling.

Frequently Asked Questions (FAQ)