Core Web Vitals are three metrics Google uses to measure how real visitors experience a page: how fast the main content loads, how quickly the page responds to a click or tap, and how much the layout shifts while loading. Google reports them in Search Console from real user data, not lab tests.
Google’s own wording on rankings is careful. Its Core Web Vitals documentation recommends good scores “for success with Search,” and says they align with what its core ranking systems seek to reward. That stops short of calling them a direct ranking factor. In my client work, I’ve never seen a Core Web Vitals fix on its own move rankings. I still fix them by default on every technical audit, because a slow or jumpy page loses visitors, and lost visitors cost you leads.
The three metrics and their targets
| Metric | What it measures | Good score |
|---|---|---|
| Largest Contentful Paint (LCP) | Loading: how long until the main content appears | Within 2.5 seconds |
| Interaction to Next Paint (INP) | Responsiveness: how quickly the page reacts to clicks, taps and typing | Under 200 milliseconds |
| Cumulative Layout Shift (CLS) | Visual stability: how much content moves around while loading | Under 0.1 |
Older guides list First Input Delay as the responsiveness metric. Google’s current list uses INP.
Lab scores and field data
Google describes Core Web Vitals as measures of real-world user experience. That’s why a PageSpeed Insights lab score of 95 can sit alongside a failing Search Console report: the lab tests one simulated visit, and Search Console reflects what real visitors on real devices and connections experienced. Judge your site on the field data, and use lab tools to find out why it fails.
Where B2B sites lose points
Buyers who reach a B2B site are often comparing vendors and ready to act. A demo request form that lags when they type, or a page that shifts just as they reach for the button, costs a lead the analytics won’t explain. The usual causes are third-party scripts: chat widgets, cookie banners, tag managers stacked with marketing pixels, and embedded videos. Each one is a reasonable tool on its own, and together they slow the page.
How to check and fix
- Start with the Core Web Vitals report in Search Console, which groups failing URLs by issue.
- Test individual URLs in PageSpeed Insights to see what slows them.
- Fix templates, not single pages. Most problems come from a shared header, footer or script.
- Review third-party scripts and remove any your team no longer uses.
- Set image and embed dimensions so content doesn’t jump while loading.
Common mistakes
- Chasing a perfect lab score while the field data still fails.
- Expecting a speed fix to rescue rankings that weak content is holding back.
- Adding a new marketing script without checking what it does to INP.
- Fixing one page instead of the template it shares with the rest of the site.
Related terms
On-page SEO · Crawl budget · Organic traffic · Lead generation SEO
