Core Web Vitals Explained in Plain English (and How to Fix a Slow WordPress Site)

Core Web Vitals are 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 tap something, and whether things jump around while it loads. They are part of Google's page experience signals, and more importantly, they track the things that make people leave a slow site.

This guide explains each metric in plain English, shows you how to test your own pages, and lists the fixes that make the biggest difference on a typical WordPress site.

In this article

1. The three Core Web Vitals
   • LCP: "When can I see it?"
   • INP: "Does it respond when I tap?"
   • CLS: "Stop moving!"
2. How to measure your site
3. Fixing LCP on WordPress
4. Fixing INP on WordPress
5. Fixing CLS on WordPress
6. How much do Core Web Vitals affect rankings?
7. A quick checklist

The three Core Web Vitals

Google assesses these at the 75th percentile of real visits, which means at least three out of four visits should hit the "good" mark. INP replaced the older First Input Delay (FID) metric in March 2024, so guides that still talk about FID are out of date.

LCP: "When can I see it?"

LCP is about perceived loading speed. If your page shows a big featured image at the top, that image is usually the LCP element. Slow hosting, huge image files and render-blocking scripts are the usual causes of a poor LCP.

INP: "Does it respond when I tap?"

INP measures the delay between a user interaction and the next visual update. If someone taps your menu button and nothing happens for half a second, that is poor INP. It is almost always caused by too much JavaScript running in the browser, often from plugins, page builders, chat widgets and third-party trackers.

CLS: "Stop moving!"

CLS measures visual stability. You have experienced bad CLS when you go to tap a link and an ad or image loads above it, pushing the link down so you tap the wrong thing. Images without dimensions, late-loading ads and web fonts that swap in are common causes.

How to measure your site

1. PageSpeed Insights (pagespeed.web.dev) — paste a URL. The top section shows field data from real Chrome users if your site has enough traffic; the lower section is a lab test. Field data is what matters for search; lab data is useful for debugging.
2. Google Search Console — the Core Web Vitals report groups your URLs into good, needs improvement and poor, separately for mobile and desktop.
3. Chrome DevTools — the Performance panel shows live LCP, INP and CLS values as you use your own page.

Fixing LCP on WordPress

• Use decent hosting with server caching. If your server takes a second to start responding (Time to First Byte), you have already lost much of your 2.5-second budget. Managed WordPress hosting with built-in caching (for example LiteSpeed Cache on LiteSpeed servers) helps a lot.
• Compress and resize images. A 4,000-pixel photo straight from a phone has no business on a blog. Resize to the largest size it will display at and serve WebP or AVIF.
• Do not lazy-load the hero image. Lazy loading is great for images further down, but the main image at the top should load immediately. Modern themes set fetchpriority="high" on it.
• Remove render-blocking CSS and JavaScript. Defer scripts that are not needed for the first view and avoid loading a heavy page builder's assets on every page.
• Use a CDN if your visitors are spread across countries.

Fixing INP on WordPress

• Audit your plugins. Deactivate anything you do not truly need. Sliders, social feeds, popup builders and multiple analytics tools are frequent offenders.
• Choose a lightweight theme. A theme that ships without jQuery and with minimal JavaScript starts you in a good place.
• Delay third-party scripts. Chat widgets, heatmaps and social embeds can usually load after the user first scrolls or interacts.
• Limit ad density. Ads load a lot of JavaScript. A few well-placed units often earn as much as a page crammed with them, while hurting speed far less.

Fixing CLS on WordPress

• Always set image width and height. WordPress does this automatically for images inserted through the editor; check custom code and older posts.
• Reserve space for ads. Give ad containers a minimum height so the content does not jump when the ad arrives.
• Be careful with web fonts. System fonts cause no shift at all. If you use custom fonts, preload them and use font-display: swap with a similar fallback.
• Do not insert banners above existing content after the page has loaded (cookie bars should overlay, not push).

How much do Core Web Vitals affect rankings?

Honestly: less than content. Google has said that great page experience does not override relevance, so a fast page with weak content will not beat a slower page that answers the question better. But when competing pages are similarly useful, experience can be a tie-breaker. The bigger reason to care is people. Slow, jumpy pages lose readers before they read anything, and for an ad-supported site that is lost revenue.

A quick checklist

1. Test your homepage and one typical article on PageSpeed Insights (mobile).
2. Turn on server or plugin caching.
3. Compress images and convert to WebP.
4. Remove plugins you do not use.
5. Make sure ad slots have reserved height.
6. Re-test, then check the Search Console report over the following 28 days, since field data updates gradually.