If you have been told your website "fails Core Web Vitals" and you are not sure what that means, this post is for you. No jargon, no developer lecture — just what the three metrics are, why Google cares, and what you can do about it.

What Core Web Vitals actually are

Core Web Vitals are three measurements Google takes of your website every time a real visitor loads it. They are not opinions — they are hard numbers, collected anonymously from Chrome users worldwide, and averaged over a 28-day window. Google uses them as one of the signals that decide whether your page ranks above or below your competitors.

The three metrics are:

1. Largest Contentful Paint (LCP)

Plain English: How long does the biggest thing on your page take to appear?

The "biggest thing" is usually your hero image, main headline, or product photo. If a visitor has to stare at a blank screen for four seconds before anything shows up, your LCP is bad.

  • Good: Under 2.5 seconds.
  • Needs improvement: 2.5–4 seconds.
  • Poor: Over 4 seconds.

2. Interaction to Next Paint (INP)

Plain English: When a visitor taps a button or link, how long until the page responds?

If there is a noticeable delay between tapping and anything happening, your INP is bad. People assume the page is broken and leave.

  • Good: Under 200 milliseconds.
  • Needs improvement: 200–500 ms.
  • Poor: Over 500 ms.

3. Cumulative Layout Shift (CLS)

Plain English: Does stuff jump around the page while it loads?

You know the feeling: you are about to tap a link, an ad pops in above it, and you accidentally tap the ad. That is CLS. High scores mean the page is visually unstable — images loading without reserved space, fonts swapping in and reflowing text, ads or banners pushing content.

  • Good: Under 0.1.
  • Needs improvement: 0.1–0.25.
  • Poor: Over 0.25.

Why Google cares

These three metrics correspond to the three moments a user judges your site:

  • "Did anything show up?" (LCP)
  • "Does it respond to me?" (INP)
  • "Is it stable enough to use?" (CLS)

Fail any of them, and the user has a bad experience. Google's job is to rank pages that users like. So Google measures the things that predict user satisfaction, and rewards pages that do well on them. It is not personal — it is just the ranking signal.

How to check your own site

Three ways, in order of ease:

1. PageSpeed Insights (easiest)

Go to pagespeed.web.dev, paste your homepage URL, and hit analyze. You will see both mobile and desktop scores. Look at the "Core Web Vitals Assessment" block at the top.

  • Green circle = passing, good.
  • Yellow = borderline, needs work.
  • Red = failing, costing you rankings.

2. Google Search Console (if you have access)

Under "Experience → Core Web Vitals", Google shows you which pages on your site are passing and failing, based on real user data. This is the most accurate view because it uses actual visits, not lab tests.

3. Chrome DevTools (for developers)

Open the site in Chrome, right-click → Inspect → Lighthouse tab → "Analyze page load". You get the same scores plus a list of specific things to fix.

What to do if you are failing

The fixes depend on which metric is failing. Common culprits:

LCP problems:

  • Huge unoptimized hero images.
  • Slow server response time.
  • Render-blocking CSS or JavaScript.
  • Fonts loading too late.

INP problems:

  • Too much JavaScript running on the main thread.
  • Heavy third-party scripts (chat widgets, tag managers, ad networks).
  • Unoptimized React/Vue re-renders.

CLS problems:

  • Images without width/height attributes.
  • Fonts swapping in after load (FOUT) and reflowing text.
  • Ads or banners injected above existing content.
  • Cookie consent banners that push everything down.

I cover the full technical fixes in What Makes a Website Fast.

The honest truth about fixes

Most small business sites fail Core Web Vitals not because of one dramatic problem, but because of dozens of small ones that accumulated over years. A plugin here, a tracking script there, a heavy theme, an unoptimized photo, a font subset that never got trimmed.

You can usually recover one or two metrics with targeted fixes. Recovering all three on an aging WordPress site often costs more than a clean rebuild on a modern stack. I wrote about that trade-off in Why Your WordPress Site Is Slow.

Why this matters commercially

Core Web Vitals are not an abstract technical score. They correlate with:

  • Search rankings — Google uses them as a direct ranking factor.
  • Conversion rate — sites that load in under 2 seconds convert roughly 2x better than sites that take 5 seconds.
  • Bounce rate — 53% of mobile visitors leave if a page takes longer than 3 seconds to load.
  • Cost per acquisition — if you run paid ads, a slow landing page means you pay for clicks that never convert.

Fixing Core Web Vitals is not a vanity project. It is one of the highest-ROI things you can do to your website.

Work with me

If your site is failing Core Web Vitals and you want an honest, free assessment of what it would take to fix, email info@tonibarisic.com or use the contact form. I can usually tell within 30 minutes whether it is a targeted fix or a rebuild.