Core Web Vitals on WordPress: Fixing LCP, INP and CLS Step by Step

WordPress powers a huge share of the web, and many of those sites struggle with speed. The reason is rarely WordPress itself — it’s heavy themes, stacks of plugins and third-party scripts. Here’s how I approach Core Web Vitals on WordPress on client sites.

Understand the three metrics#

Google assesses these at the 75th percentile of page loads, separately for mobile and desktop. Learn more in the Core Web Vitals library entry.

Measure correctly first#

1. Search Console → Core Web Vitals: groups of URLs that pass or fail, based on real Chrome users (CrUX data).
2. PageSpeed Insights: the top section shows field data for the URL or origin; the bottom section is a Lighthouse lab test useful for diagnosis.
3. Chrome DevTools → Performance panel: record an interaction to see exactly which scripts slow INP.

Fixing slow LCP#

1. Start with hosting and caching#

If your server takes over a second to respond (Time to First Byte), every metric suffers. Use quality managed or cloud hosting with a data centre near your audience (Mumbai or Singapore for Indian visitors), enable full-page caching, and put a CDN in front of the site.

2. Optimise the LCP image#

• Serve it in WebP or AVIF at the correct display size, with srcset.
• Never lazy-load the LCP image. Add fetchpriority="high" to it.
• Avoid hero sliders; a single static image or text headline is faster and usually converts better.
• Preload the LCP image if it’s a CSS background.

3. Reduce render-blocking resources#

• Remove unused plugin CSS/JS on pages that don’t need it (many optimisation plugins can do this per page).
• Inline critical CSS and defer the rest.
• Limit web fonts to one or two families and the weights you actually use; use font-display: swap and consider self-hosting.

Fixing poor INP#

INP measures responsiveness throughout the visit. The usual culprit is long JavaScript tasks blocking the main thread.

• Audit plugins: deactivate and test. Page builders, sliders, popup plugins, social feeds and some analytics add heavy JS.
• Delay third-party scripts (chat widgets, heatmaps, ad pixels) until user interaction or after load.
• Defer non-critical JavaScript and avoid jQuery-dependent plugins where lightweight alternatives exist.
• Reduce DOM size: deeply nested builder layouts make every interaction slower.
• For custom code, break up long tasks and give the browser a chance to paint between steps.

Fixing CLS#

• Always set width and height (or aspect-ratio) on images, videos and iframes.
• Reserve space for ads and embeds with fixed-size containers.
• Avoid injecting banners (cookie notices, promos) above existing content after load; overlay them instead.
• Use font-display: swap with fallback fonts of similar metrics to reduce text reflow.
• Animate with transform and opacity, not properties that change layout.

A lean WordPress stack#

Validate and monitor#

After changes, use “Validate fix” in Search Console’s Core Web Vitals report. Field data uses a rolling 28-day window, so expect results to update gradually over about four weeks. Re-test whenever you add a plugin, change the theme or install a new tracking script.

Speed is one part of the bigger picture — see the full technical SEO checklist for everything else.