If someone has told you that your WordPress site “fails Core Web Vitals,” you are not alone in wondering what that actually means. The term sounds technical, but the idea behind it is simple: Google measures how real visitors experience your pages, and it turns that experience into three numbers.
In this guide I will explain those three numbers in plain English, why they matter for your traffic and sales, and where to look to see how your own site is doing.
What Are Core Web Vitals?
Core Web Vitals are a set of metrics Google uses to describe the user experience of a web page. Each one answers a question a visitor silently asks:
- Is the page showing me something useful quickly? That is Largest Contentful Paint (LCP).
- Does the page react when I tap or click? That is Interaction to Next Paint (INP).
- Does the page stay still while I read it? That is Cumulative Layout Shift (CLS).
They are measured on real devices, for real visitors, and then summarized for each page or for your whole site.
The Three Metrics and Their Targets
Largest Contentful Paint (LCP)
LCP measures how long it takes for the biggest visible element, usually a hero image or a large heading, to appear. Google considers an LCP of 2.5 seconds or less good, and anything above 4 seconds poor. If your homepage looks blank for several seconds on a phone, this is the number that suffers.
Interaction to Next Paint (INP)
INP measures how quickly your page responds when someone taps a menu, opens a filter or clicks add to cart. It replaced the older First Input Delay metric in March 2024. A good INP is 200 milliseconds or less, and anything above 500 milliseconds is poor. Slow responses usually come from heavy JavaScript.
Cumulative Layout Shift (CLS)
CLS measures unexpected movement. You have felt it when you go to tap a button and the page jumps, so you tap something else. A good CLS score is 0.1 or lower, and anything above 0.25 is poor.
Why Business Owners Should Care
There are two practical reasons.
First, visibility. Google has said that Core Web Vitals are used by its ranking systems as part of the page experience signals. They will not rescue thin content, and great content can still rank with average speed. But when two pages are similarly relevant, a faster and more stable page has the edge, and a page that fails badly can hold you back.
Second, and more important, money. A slow or jumpy page frustrates people before they ever read your offer. Visitors leave, forms go unfilled and carts are abandoned. Speed is not a technical checkbox, it is part of how your business looks and feels to a stranger on a phone.
Field Data vs Lab Data
This is the part most people miss. There are two ways to measure Core Web Vitals:
- Field data comes from real Chrome users visiting your site, collected over the previous 28 days. This is what Google uses.
- Lab data comes from a simulated test, such as Lighthouse, run once under fixed conditions.
Lab tools are excellent for debugging, but they are a snapshot. Field data is the truth. I explain the difference in more detail in Lighthouse vs Field Data.
Google also looks at the 75th percentile. For a page to pass, at least 75 percent of visits need to hit the good threshold for each metric, measured separately on mobile and desktop.
How to Check Your Own Site
You can see your numbers for free in a few minutes:
- Open PageSpeed Insights, enter your URL and look at the Discover what your real users are experiencing section at the top. That is field data.
- Open Google Search Console and go to Experience, then Core Web Vitals. It groups your URLs into Good, Needs improvement and Poor for mobile and desktop.
- Use the lab diagnostics lower on the PageSpeed Insights report to find what is causing the problem.
If you see no field data, your page may not have enough traffic yet. In that case, rely on the lab results and fix the obvious issues first.
What Usually Causes Failures on WordPress
After auditing many WordPress sites, the same causes appear again and again:
- Slow server response and missing page caching, which delays everything, including LCP.
- Oversized or lazy-loaded hero images that appear late.
- Too many plugins and third-party scripts such as chat widgets and trackers, which hurt INP.
- Images, ads and embeds with no reserved space, which cause layout shifts.
- Page builders and sliders that ship far more code than the page needs.
The good news is that each of these has a clear fix. I cover them one by one in my guides to improving LCP, fixing INP and fixing CLS.
A Sensible Order of Work
You do not need to fix everything at once. Start with the metric that is failing in Search Console, fix the template that affects the most pages, and re-check after the 28-day window rolls over. Chasing a perfect 100 in a lab test is rarely worth the effort. Passing all three metrics for real visitors is the goal.
If you would rather have an expert look at it, you can request a free audit and I will show you exactly what is holding your site back.
