Core Web Vitals are three measurements Google uses to judge how a web page feels to real visitors: how quickly the main content appears, how fast the page responds when someone clicks or taps, and how stable the layout stays while it loads. Good scores won’t guarantee higher rankings, but they are part of how Google assesses page experience, and a slow or jumpy site frustrates the customers you worked hard to attract. Here is what each metric means, how to check yours and what usually fixes them.
The Three Core Web Vitals in Plain English
Largest Contentful Paint (LCP): loading
LCP measures how long it takes for the biggest visible element on the screen, usually a hero image, banner or main heading, to finish loading. In everyday terms, it answers the question: “How long until this page looks ready?”
Interaction to Next Paint (INP): responsiveness
INP measures how quickly the page reacts when a visitor interacts with it, such as clicking a button, opening a menu or typing in a form. If someone taps “Add to cart” and nothing seems to happen for a moment, that delay shows up in INP. It replaced an older metric, First Input Delay (FID), in March 2024.
Cumulative Layout Shift (CLS): visual stability
CLS measures how much the content moves around unexpectedly while the page loads. You have probably tried to tap a link only for the page to jump and send you somewhere else. That jump is a layout shift, and CLS adds them up into a single score.
Google publishes clear thresholds for each metric:
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP | Loading speed | 2.5 seconds or less | 2.5 to 4 seconds | Over 4 seconds |
| INP | Responsiveness | 200 milliseconds or less | 200 to 500 milliseconds | Over 500 milliseconds |
| CLS | Visual stability | 0.1 or less | 0.1 to 0.25 | Over 0.25 |
To pass, a page needs to hit the “good” threshold for at least 75% of real visits, measured separately for mobile and desktop. That means your site has to perform well for people on older phones and slower connections, not just on your office computer.
Why Core Web Vitals Matter for Your Business
It is easy to treat these scores as a technical box to tick, but they reflect real experiences your visitors have every day:
- Visitor experience. People are less patient with slow, unstable pages, especially on mobile. A page that loads quickly and responds instantly simply feels more trustworthy.
- Search visibility. Core Web Vitals are part of Google’s page experience signals. Relevant, helpful content still matters most, but when competing pages are similar, a better experience can help.
- Paid campaigns. If you run Google Ads, a fast, usable landing page helps make the most of every click you pay for.
- A useful health check. Poor scores often point to deeper problems, such as cheap hosting, too many plugins or a bloated theme, that are worth fixing anyway.
How to Check Your Scores
You don’t need technical tools or a developer to see where you stand. Two free Google tools cover most needs:
- PageSpeed Insights. Enter any page address at pagespeed.web.dev. The top section shows field data from real Chrome users over the last 28 days. The section below shows lab data from a simulated test, along with a performance score out of 100 and suggestions.
- Google Search Console. The Core Web Vitals report groups your pages into good, needs improvement and poor, for both mobile and desktop. It is the best way to see problems across a whole site rather than one page at a time.
The difference between field and lab data matters. Field data reflects what your real visitors experience, and it is what Google uses. Lab data is a controlled test that is useful for diagnosing problems. Smaller sites with low traffic may not have enough visits for field data, in which case the lab results are your best guide.
What Usually Causes Poor Scores
Slow LCP
- Large, uncompressed hero images or background videos.
- Slow hosting, where the server takes too long to send the first byte of the page.
- Stylesheets and scripts that must load before anything appears on screen.
- Image sliders and carousels at the top of the page.
Poor INP
- Heavy JavaScript from themes, page builders and plugins.
- Third-party scripts such as chat widgets, tracking pixels, pop-ups and embedded social feeds.
- Complex menus, filters or forms that run a lot of code on every click.
High CLS
- Images and videos without set dimensions, so the page reflows once they load.
- Ads, embeds or cookie banners that push content down after it appears.
- Web fonts that swap in late and change the size of text.
Common Fixes a Developer Will Make
Most improvements come from a handful of well-understood fixes. On a typical business site, a developer will look at:
- Image optimization: compressing images, serving modern formats like WebP or AVIF, and sizing them correctly for each screen.
- Prioritizing the main image: loading the hero image early instead of lazy-loading it.
- Better hosting and caching: faster servers, page caching and a content delivery network (CDN) that serves files from locations close to your visitors.
- Trimming JavaScript: removing unused plugins, delaying non-essential scripts and replacing heavy features with lighter ones.
- Reserving space: setting width and height on images and embeds so the layout doesn’t jump.
- Font loading: hosting fonts locally and loading only the weights you actually use.
For a longer list, see our guide to website speed optimization fixes that actually work. If your site needs a deeper rebuild, these improvements are much easier to bake in from the start, which is why we test speed as part of every custom WordPress build.
How Long Until Improvements Show Up
Lab scores in PageSpeed Insights change as soon as fixes go live. Field data takes longer because it is based on a rolling 28-day window of real visits, so expect it to take up to about four weeks for the full effect to appear in PageSpeed Insights and Search Console. Any impact on search visibility, if there is one, can take longer still and depends on many other factors.
FAQ
Do I need a perfect 100 PageSpeed score?
No. The score out of 100 is a lab estimate, and chasing a perfect number often isn’t worth the cost. What matters is passing the Core Web Vitals thresholds for real visitors and giving people a fast, stable experience.
Is WordPress slow by default?
No. WordPress itself can be very fast. Slow WordPress sites are usually caused by heavy themes, too many plugins, unoptimized images and low-cost hosting, all of which can be fixed.
Can poor Core Web Vitals hurt my rankings?
They are one signal among many. Poor scores rarely sink a page with great content on their own, and good scores won’t lift a page that doesn’t answer the searcher’s question. Think of them as part of building a site people enjoy using.
Get Your Core Web Vitals Into the Green
Web Emblem helps businesses across the United States and Canada find and fix what is slowing their sites down, from images and hosting to plugins and code. Learn more about our speed optimization and technical SEO services.
Want to know why your site is slow? Get a fixed quote within 24 hours.
