11 WordPress ServicesView all
8 industry verticalsAll industries
12 UK locationsAll locations
Home/Blog/Performance
Performance6 November 2026· 8 min read

WordPress Core Web Vitals: How to Fix LCP, CLS and INP

Google Search Console is showing Core Web Vitals failures on your WordPress site. Here is what LCP, CLS and INP actually measure and how to fix each one without a rebuild.

Google Search Console is reporting Core Web Vitals failures on your WordPress site — red or amber scores on LCP, CLS or INP. These metrics directly influence your search rankings and, more immediately, the experience of every person visiting your site. Each metric has specific, fixable causes on WordPress. Here is how to diagnose and address each one.

Fixing LCP: get your largest element loading faster

LCP measures how long it takes for the largest visible content — usually a hero image or headline — to appear. The most impactful fixes are: compress and convert your hero image to WebP format and serve it at the correct display dimensions; add a fetchpriority="high" attribute to the LCP image so the browser prioritises it; preconnect to external domains (Google Fonts, CDNs) in your document head; and move to faster hosting if your server response time (TTFB) exceeds 600ms.

WordPress speed optimisation →

Fixing CLS: prevent elements from shifting after load

CLS is caused by elements that move after the page has painted. Add explicit width and height attributes to every image in your WordPress content. Use font-display: swap in your font CSS but set size-adjust to minimise the reflow when the web font loads. If you show a cookie notice or top bar after page load, reserve its space in CSS from the start using min-height so it does not push content down.

Fixing INP: reduce JavaScript execution on the main thread

INP failures are almost always caused by JavaScript blocking the main thread. Audit your active plugins and remove any that add scripts to the front end without a clear user benefit — analytics tools, chat widgets, A/B testing scripts and social embeds are common offenders. Use a performance plugin like Perfmatters to selectively disable scripts on pages where they are not needed. Consider replacing a heavy page builder with a leaner theme.

Measure with real-user data, not just lab tools

PageSpeed Insights lab scores do not always match your Core Web Vitals in Search Console. The CrUX (Chrome User Experience Report) data in Search Console reflects real visits from Chrome users, which includes network conditions, device performance and geographic variance that lab tools cannot simulate. Fix what Search Console flags, then wait 28 days for the rolling window to update.

ImportantSites built with Elementor, Divi or WPBakery will have an inherently harder time passing Core Web Vitals than sites built on lean custom themes. Page builders load significant CSS and JavaScript globally regardless of which features each page uses. If your site is failing INP and LCP despite optimisation, the most effective long-term fix is migrating to a custom-coded WordPress theme — not adding more performance plugins on top of a heavy foundation.

Frequently asked questions

What are Core Web Vitals and why do they matter for WordPress?+

Core Web Vitals are three performance metrics Google uses as ranking signals: LCP (Largest Contentful Paint) measures how long the largest visible element takes to load, CLS (Cumulative Layout Shift) measures unexpected visual movement during loading, and INP (Interaction to Next Paint) measures how responsive the page is to user input. Sites that pass all three have a small but measurable ranking advantage, and poor scores noticeably hurt user experience.

What causes poor LCP on WordPress sites?+

The most common causes of slow LCP on WordPress are: unoptimised hero images served without modern formats like WebP, render-blocking CSS or JavaScript delaying the display of the main content, slow server response times on cheap shared hosting, and large page builders like Elementor loading excessive CSS and JavaScript before the visible content.

What causes CLS on WordPress sites?+

CLS is caused by elements that shift position after the page has painted. The most common WordPress causes are images without explicit width and height attributes, fonts loading and causing text to reflow (FOUT), late-loading ads or embeds that push content down, and banners or cookie notices appearing after initial render without reserved space.

What is INP and how do I fix it on WordPress?+

INP replaced FID in 2024 and measures the responsiveness of all interactions, not just the first. Poor INP on WordPress is usually caused by heavy JavaScript from page builders, tracking scripts and plugins executing on the main thread. Deferring non-essential scripts, removing unused plugins and switching from a page builder to a custom theme are the most effective fixes.

Related service

Fixing Core Web Vitals on a WordPress site with page builders and multiple plugins is technical work. Our speed optimisation service diagnoses your exact failures with real-user data and implements the fixes that move the metrics that matter.

WordPress Speed Optimisation →

Next article

Performance

WordPress PageSpeed Score Low? The 8 Fixes That Actually Move the Needle

→
← All articles