Core Web Vitals on WordPress: How to Pass in 2026

What are Core Web Vitals?

Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors. They're part of Google's page experience signals, and they matter even more for conversions: slow, jumpy pages lose enquiries. This guide shows how to pass Core Web Vitals on WordPress without rebuilding your site.

INP replaced First Input Delay (FID) as a Core Web Vital in March 2024. It's stricter, because it measures every interaction on the page, not just the first one.

Measure before you change anything

• Search Console's Core Web Vitals report: real-user data grouped by similar pages. This is what Google uses.
• PageSpeed Insights: real-user data for a single URL (if available) plus a lab test with specific suggestions.
• Chrome DevTools: the Performance panel shows exactly which scripts and elements cause problems.

Start with hosting and caching

No plugin can fully fix a slow server. A slow server response delays everything, especially LCP.

1. Use quality hosting with servers in or near the UK, a current PHP version and enough resources for your traffic.
2. Turn on page caching through your host or a caching plugin, so pages aren't rebuilt for every visitor.
3. Use object caching (such as Redis) for busy or WooCommerce sites, if your host supports it.
4. Add a CDN to serve images and files quickly across the country.

Fix LCP: load the main content faster

On most WordPress pages, the LCP element is the hero image or the main heading. To speed it up:

• Compress and resize images and serve WebP or AVIF versions.
• Don't lazy-load the hero image; lazy-load images further down the page instead.
• Give the hero image priority (fetchpriority="high" or a preload) so it starts downloading straight away.
• Avoid sliders and heavy background videos in the hero area.
• Reduce render-blocking CSS and JavaScript, and load fonts efficiently with a fallback.

Fix INP: make the page respond quickly

INP problems happen when the browser is too busy running JavaScript to respond to a tap. On WordPress, the usual culprits are plugins, page builders and third-party scripts.

• Audit your plugins: remove ones you don't need, and replace heavy ones with lighter alternatives.
• Load scripts only where they're used, for example form scripts only on pages with forms.
• Delay non-essential third-party scripts such as chat widgets and social embeds until after interaction.
• Simplify page builder layouts: fewer nested sections, widgets and animations.
• Review tag manager containers for old or duplicate tracking tags.

Fix CLS: stop the layout jumping

• Set width and height on images, videos and embeds so the browser reserves space.
• Reserve space for banners, cookie notices and ads instead of pushing content down.
• Load web fonts carefully so text doesn't jump when the font arrives.
• Avoid inserting content above what the visitor is already reading.

Tips for Elementor sites

1. Switch on Elementor's built-in performance features, such as optimised asset loading and improved CSS loading.
2. Use containers (Flexbox or Grid) instead of older nested sections and columns.
3. Limit entrance animations, especially above the fold.
4. Use one or two font families, and host fonts locally where possible.
5. Keep global widgets and templates lean; heavy headers and footers load on every page.

Common mistakes

• Chasing a perfect lab score instead of passing real-user Core Web Vitals.
• Stacking several caching or optimisation plugins that conflict.
• Uploading full-size photos straight from a camera or phone.
• Lazy-loading the hero image.
• Adding a new script or plugin for every small feature.
• Not re-testing after theme, plugin or page builder updates.

Core Web Vitals are one part of technical SEO. Our technical SEO guide covers crawling, indexing and the rest.