Core Web Vitals are Google’s three measures of how a page feels to the person using it: how quickly the main content appears, how quickly the page responds when you tap or click, and whether things jump around while it loads. They’re a ranking signal, but the better reason to care is simpler: slow, jumpy pages lose visitors.
Here’s what each one measures, how to test them properly, and the fixes I reach for first on WordPress sites.
The three metrics
- Largest Contentful Paint (LCP): how long until the biggest thing in view, usually a hero image or headline, has loaded. Good is 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page responds to taps, clicks and key presses, across the whole visit. Good is 200 milliseconds or less. INP replaced First Input Delay as a Core Web Vital in March 2024.
- Cumulative Layout Shift (CLS): how much the layout moves unexpectedly while you’re reading. Good is 0.1 or less.
Google looks at the 75th percentile of real visits, so a page has to be fast for most of your visitors, not just for you on office Wi-Fi.
Measure first
- Run the page through PageSpeed Insights. The top section is field data from real Chrome users; the lower section is a lab test. When they disagree, the field data is what counts.
- Open the Core Web Vitals report in Google Search Console to see which groups of pages fail, not just one URL.
- Test on mobile. Most problems show up on a mid-range phone on a mobile connection long before they show up on a laptop.
- Test each page type: home, a post, a product, a landing page. They’re usually built differently and fail for different reasons.
Fixing LCP
- Find the LCP element. PageSpeed Insights names it, and everything else depends on what it is.
- Don’t lazy-load it. Lazy loading is right for images further down the page and wrong for the first one. Give the hero image
fetchpriority="high"instead. - Serve the right size. A 2,000-pixel image squeezed into a 400-pixel space wastes time. Use responsive images and a modern format such as WebP or AVIF.
- Speed up the server. If the first byte takes a second to arrive, nothing on the page can be fast. Page caching and decent hosting fix this; I covered how to choose hosting separately.
- Cut render-blocking files. Every stylesheet and script in the head has to load before the page can draw, and many plugins load their files on every page, even where they aren’t used.
- Self-host fonts and use
font-display: swap, so text appears straight away.
Fixing INP
- Find the heavy JavaScript. Sliders, chat widgets, pop-ups, tracking tags and some page-builder add-ons run a lot of script when the page loads and when people interact with it.
- Delay or remove third-party scripts. Load chat and marketing tags after the page is usable, or only on the pages that need them.
- Keep the page smaller. Very large pages, with thousands of nested elements, are slower to update when someone interacts. Builders that wrap every element in several containers make this worse.
- Break up long tasks. In custom code, split heavy work into smaller pieces so the browser can respond in between.
Fixing CLS
- Give images and embeds dimensions. Width and height attributes, or a CSS aspect ratio, let the browser reserve the space before the file arrives.
- Reserve space for things that appear late: cookie banners, announcement bars, ads and embedded videos.
- Tame font swaps. A fallback font with different proportions makes text reflow when the web font arrives. Matching the fallback’s size reduces the jump.
- Don’t insert content above what’s already on screen, unless it’s in response to something the visitor did.
WordPress-specific wins
- Audit plugins. Deactivate them one at a time on a staging copy and measure. A single plugin can account for a large share of the scripts on a page.
- Use the caching plugin that matches your server, such as LiteSpeed Cache on a LiteSpeed server.
- Optimise images on upload, and convert the existing media library too.
- Choose a lean theme or builder. The markup a builder produces sets a floor on how fast a page can be. I compared two popular ones in Bricks vs Elementor.
Check, then check again
Re-test in the lab after each change, so you know what helped. Field data takes longer: the Chrome UX Report uses a rolling 28-day window, so improvements show up in PageSpeed Insights and Search Console over the following weeks.
If you’d like someone to find and fix the slow parts for you, that’s what my website speed optimisation work covers: measured before, fixed in order of impact, and measured again.