Skip to content
Your Tech Read
Your Tech Read
Web & Cloud Hosting

Core Web Vitals Explained: How to Check and Fix Them on WordPress

In this article 11 sections
  1. What Are Core Web Vitals?
  2. Why They Matter
  3. The Three Core Web Vitals
  4. The Scores You’re Aiming For
  5. How to Check Your Core Web Vitals
  6. How to Fix Core Web Vitals on WordPress
  7. What Works for Us
  8. Mistakes to Avoid
  9. How Long Before Google Notices?
  10. Frequently Asked Questions
  11. The Final Word

Core Web Vitals sound like something only developers should worry about, a jumble of acronyms like LCP, INP and CLS. But behind the jargon sits a very human question: does your website feel fast and comfortable to use, especially on a phone?

I care about this for every site I run. On my own WordPress sites, the speed basics are LiteSpeed Cache, Cloudflare in front of the site, and images saved as WebP and kept under 100 KB each. Those three habits do most of the heavy lifting. Yet when I ran our own homepage through Google’s test for this guide, it still found one thing to improve, which is exactly why these checks are worth doing even when you think everything’s fine.

What Are Core Web Vitals?

Core Web Vitals are three measurements Google uses to judge the real-world experience of a web page: how quickly the main content loads, how fast the page responds when someone taps or clicks, and how stable the layout stays while it loads.

Why They Matter

  • They’re part of Google’s ranking signals. They won’t push poor content to the top, but when two pages are equally helpful, the faster, smoother one has an edge.
  • They affect your visitors directly. Slow pages and jumpy layouts make people leave, especially on mobile data.
  • They reflect real users. Google measures them from actual Chrome visitors, not just a lab test, so passing them means real people are having a good experience.

The Three Core Web Vitals

Google measures three things, each one a slightly different feeling a visitor has while using your page.

LCP: Largest Contentful Paint (Loading)

LCP measures how long it takes for the biggest visible thing on the screen, usually the featured image or the main heading, to appear. It’s the moment a visitor feels the page has actually loaded. Slow hosting, heavy images and too much code before the content are the usual culprits.

INP: Interaction to Next Paint (Responsiveness)

INP measures how quickly your page reacts when someone taps a button, opens a menu or types in a form. It replaced the older FID metric in 2024. A poor INP feels like a page that’s “stuck” or laggy, usually because heavy JavaScript is keeping the browser busy.

CLS: Cumulative Layout Shift (Visual Stability)

CLS measures how much the page jumps around while it loads. You’ve felt this one: you go to tap a link, an ad or image suddenly loads above it, and you tap the wrong thing. Images without set sizes, late-loading ads and web fonts swapping in are the common causes.

The Scores You’re Aiming For

Google judges each metric at the 75th percentile of real visits, meaning three out of four visitors should get a good experience.

Metric Good Poor
LCP (loading) 2.5 seconds or less More than 4 seconds
INP (responsiveness) 200 milliseconds or less More than 500 milliseconds
CLS (visual stability) 0.1 or less More than 0.25

Anything between “good” and “poor” is labelled Needs improvement. To pass Core Web Vitals, a page needs all three in the good range.

How to Check Your Core Web Vitals

Option 1: PageSpeed Insights

Go to pagespeed.web.dev, paste in any page from your site and click Analyze. You’ll get two kinds of results:

  • Real user data (field data) at the top, under “Discover what your real users are experiencing”. This comes from actual Chrome users visiting your site over the past 28 days, and it’s what Google uses for ranking.
  • Lab data below, under “Diagnose performance issues”. This is a one-off simulated test with a performance score out of 100 and a list of things to fix. It’s perfect for diagnosing problems, but it isn’t what Google ranks you on.

Always check the Mobile tab first. Google ranks most sites based on their mobile experience, and mobile scores are almost always lower than desktop.

Option 2: Google Search Console

In Search Console, open Experience → Core Web Vitals. It groups your pages into Good, Needs improvement and Poor for both mobile and desktop, and shows exactly which issue affects which group of pages. This is the best place to see the big picture across your whole site.

What Our Own Site Shows

When we tested the YourTechRead homepage in PageSpeed Insights in November 2026, the lab results came back at 89 for performance on mobile and 99 on desktop, with 98 for accessibility and 100 for both best practices and SEO.

Digging into the numbers told a clear story:

Metric Mobile Desktop
Largest Contentful Paint 3.6 s (needs improvement) 0.9 s (good)
Cumulative Layout Shift 0 (good) 0.001 (good)
Total Blocking Time 50 ms (good) 10 ms (good)
First Contentful Paint 0.9 s 0.7 s

Everything was green except one thing: LCP on mobile, at 3.6 seconds. The page starts showing content quickly and the layout doesn’t jump at all, but the biggest element near the top, the featured image of the latest article, takes longer to appear over a simulated slow 4G connection. That single metric is what’s holding mobile at 89 instead of 90-plus, and PageSpeed’s own suggestions point to why. It flagged render-blocking requests (an estimated 310 ms saving), cache lifetimes that could be longer (about 151 KiB saved on repeat visits) and a small amount of legacy JavaScript. So our to-do list is clear: let the caching plugin defer non-critical CSS and scripts, set longer browser-cache times, and preload that top featured image while excluding it from lazy loading. Our images are already WebP and under 100 KB each, so the remaining gains are in how and when the image loads, not its size.

That’s the real value of these tests. Instead of trying to fix everything, they point you to the one thing that matters most.

But the most interesting part was at the top: “No Data” for real users. That’s completely normal for a newer site. Google only shows field data once enough Chrome users have visited a page to make the numbers reliable. Until then, you can only work from lab scores, and Search Console’s Core Web Vitals report may also say there isn’t enough data yet.

So if your new site shows “No Data”, don’t panic. Focus on getting your lab scores healthy, especially on mobile, and the real-user data will appear as your traffic grows.

How to Fix Core Web Vitals on WordPress

You don’t need to be a developer for most of these. Work through them roughly in order, testing after each change.

Improve LCP (Loading Speed)

  • Use a caching plugin. LiteSpeed Cache (if your host runs LiteSpeed servers) or WP Rocket serve ready-made pages instead of building them on every visit. Our LiteSpeed Cache vs WP Rocket comparison helps you choose.
  • Compress and resize images. Upload images no wider than your content area, and convert them to WebP. Most caching plugins and image tools like ShortPixel or Imagify do this automatically.
  • Don’t lazy-load the main image. Lazy loading is great for images further down, but the featured image at the top should load immediately. Good caching plugins let you exclude it.
  • Choose decent hosting. Slow server response (TTFB) drags down LCP no matter what else you do. Our best web hosting in India guide covers fast options.
  • Use a CDN like Cloudflare to serve files from a location close to your visitors.

Improve INP (Responsiveness)

  • Cut unnecessary plugins, especially ones that add sliders, pop-ups, chat widgets or tracking scripts to every page.
  • Delay non-essential JavaScript until the visitor interacts. LiteSpeed Cache and WP Rocket both have a “delay JS” option.
  • Be careful with heavy page builders on simple pages. Elementor is wonderful to build with, but a lighter theme or the block editor can be faster for plain articles.
  • Limit third-party embeds such as social feeds and multiple ad networks.

Improve CLS (Visual Stability)

  • Set width and height on images and videos, so the browser reserves space before they load. WordPress does this for images added through the editor.
  • Reserve space for ads and embeds with a fixed-height container.
  • Load fonts properly. Use font-display: swap and preload your main font, or stick to system fonts, so text doesn’t jump when the web font arrives.
  • Avoid pop-ups and banners that push content down. Overlays that float on top are less disruptive.

If your whole site feels slow rather than just failing one metric, start with our broader guide to speeding up a slow WordPress site.

What Works for Us

On our own WordPress sites, three habits handle most of the work:

  • LiteSpeed Cache builds fast, ready-made pages and takes care of things like minifying files and delaying scripts.
  • Cloudflare sits in front of the site, serving files from servers near the visitor and adding a layer of protection. Our Cloudflare for beginners guide shows how to set it up.
  • WebP images under 100 KB keep pages light without visibly hurting quality.

With those in place, our homepage scores 99 on desktop and 89 on mobile, and the only thing left to polish is mobile LCP. That’s typical: once the basics are right, Core Web Vitals work becomes about small, targeted fixes rather than big overhauls.

Mistakes to Avoid

  • Chasing a perfect 100. A lab score in the 90s on mobile is excellent. Real-user data in the green matters far more than the number in the circle.
  • Only testing on desktop. Mobile is where most problems hide, and it’s what Google mostly uses.
  • Installing two caching plugins. They fight each other and can break your site. Pick one.
  • Lazy-loading everything, including the main image at the top, which can actually make LCP worse.
  • Testing once and forgetting. New plugins, themes and ads can quietly slow things down, so recheck after big changes.

How Long Before Google Notices?

PageSpeed’s lab test updates instantly, so you’ll see the effect of a fix straight away. Real-user data, the part Google uses for rankings, is based on the previous 28 days, so improvements show up gradually over about a month. In Search Console, after fixing an issue, you can click Validate fix in the Core Web Vitals report, and Google will monitor the pages over the following weeks.

Frequently Asked Questions

Do Core Web Vitals affect SEO?

Yes, they’re part of Google’s page experience signals. They’re not as important as helpful, relevant content, but when pages are otherwise similar, better Core Web Vitals can give you an edge, and they also keep visitors from leaving.

What is a good LCP score?

A good Largest Contentful Paint is 2.5 seconds or less, measured at the 75th percentile of real visits. Between 2.5 and 4 seconds needs improvement, and over 4 seconds is poor.

What replaced FID in Core Web Vitals?

Interaction to Next Paint (INP) replaced First Input Delay (FID) in March 2024. INP measures how quickly a page responds to all of a visitor’s interactions, not just the first one.

Why does PageSpeed Insights say “No Data”?

It means Google doesn’t yet have enough real Chrome users visiting that page or site to show reliable field data. It’s normal for new or low-traffic sites. You can still use the lab results below it to find and fix problems.

Why is my mobile score lower than desktop?

PageSpeed simulates a mid-range phone on a slow 4G connection for the mobile test, so heavy images, scripts and fonts hurt much more than on a fast desktop. Most sites score lower on mobile.

Which WordPress plugin is best for Core Web Vitals?

A good caching plugin makes the biggest difference. LiteSpeed Cache is excellent and free if your host uses LiteSpeed servers, while WP Rocket is a popular paid option that works on any host.

The Final Word

Core Web Vitals boil down to three questions: does the page load quickly, does it respond when I tap, and does it stay still while I read? Get those right and both Google and your visitors will notice.

You don’t need to be a developer to make real progress. A good caching plugin, a CDN like Cloudflare and lightweight images will carry most sites into the green, and PageSpeed Insights will happily point out whatever’s left. Run your own site through it tonight; like ours, it’ll probably show you the one fix that matters most.

Leave a comment

Your email address will not be published. Required fields are marked *