Core Web Vitals: the three numbers that decide if Google bothers.

Google uses Core Web Vitals as a direct ranking signal. If your scores fall below the threshold on any of the three metrics, Google treats your page as a poor experience — and ranks it accordingly. That is not a theory. Google confirmed it as part of the Page Experience update, and it has been baked into the core algorithm since 2021.

Most professional services firms ignore this. They spend money on content, backlinks, and ads — then wonder why pages with thin competition still sit on page two. The answer is often technical. A slow, jumpy, unresponsive page tells Google one thing: users will not like it here.

What are the three Core Web Vitals?

The three metrics are Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). Each one measures something different about the experience of loading and using a page.

LCP — Largest Contentful Paint measures how long it takes for the biggest visible element on the page to load. That element is usually a hero image, a large block of text, or a video thumbnail. Google considers anything under 2.5 seconds good. Between 2.5 and 4 seconds needs improvement. Over 4 seconds is poor.

INP — Interaction to Next Paint replaced First Input Delay (FID) in March 2024. It measures the time between a user doing something — clicking a button, tapping a link, submitting a form — and the browser visually responding. Under 200 milliseconds is good. 200–500ms needs improvement. Over 500ms is poor.

CLS — Cumulative Layout Shift measures visual instability. If elements move around while the page loads — a button that jumps before you tap it, a paragraph that shifts when an ad loads above it — that is layout shift. A CLS score under 0.1 is good. 0.1–0.25 needs improvement. Over 0.25 is poor.

These thresholds are not arbitrary. Google derived them from Chrome usage data across billions of page loads. They represent the point at which real users, measured in aggregate, report worse experiences.

Why does Google care about these specific numbers?

Google's business depends on search results being useful. If users click a result and bounce because the page is slow or broken, that is a signal Google has failed — not just the site owner. Core Web Vitals give Google a proxy for page quality that does not rely on self-reported data or easy manipulation.

Links can be bought. Reviews can be faked. CLS cannot be faked. LCP is measured against real user data collected through Chrome — what Google calls field data — not just a lab test you run once. Your page either loads fast for real users or it does not.

The field data distinction matters. Google uses the Chrome User Experience Report (CrUX) to collect real-world performance from actual visits to your site. If your site is new or low-traffic, there may not be enough field data for Google to score it — in which case Google falls back to lab data from tools like Lighthouse. But the moment you have traffic, field data takes over. You cannot optimise your way past it with a single clean test.

How do you check your own scores?

Four tools are worth knowing: PageSpeed Insights, Search Console, Lighthouse, and CrUX Dashboard.

PageSpeed Insights (pagespeed.web.dev) gives you both field and lab data for any URL. It is the fastest starting point. Paste your URL, read the verdict. If field data is available, that is your real score. Lab data tells you what to fix.

Google Search Console has a Core Web Vitals report under the Experience section. It shows you which URLs are failing, which need improvement, and which are good — grouped by issue type. This is the most actionable view for fixing problems at scale because it groups similar pages together.

Lighthouse is the auditing tool built into Chrome DevTools. Open DevTools (F12), go to the Lighthouse tab, and run an audit. It gives lab scores only, but the diagnostic detail — which resources are blocking render, which images lack dimensions, which scripts fire too late — is more useful for developers than a headline score.

CrUX Dashboard (via Google Data Studio / Looker Studio) lets you track your field data over time. If you made a performance change three months ago, the CrUX Dashboard will show you whether it moved the needle with real users.

For professional services firms, Search Console is where to start. It tells you which specific pages are failing in the field — not hypothetically, but factually.

What actually causes poor scores?

For most professional services sites, the culprits are predictable. They fall into three categories: images, third-party scripts, and fonts.

Images are the leading cause of poor LCP. A hero image that is 2MB, served without modern compression, with no explicit width and height attributes set — that is a textbook LCP problem and a CLS problem at the same time. The browser has to download the full image before it knows how big it is, so the layout shifts. Compress images, serve WebP format, set explicit dimensions, and use `loading=