At some point, somebody is going to say the words "Core Web Vitals" to you. Maybe it's an agency pitching you an audit. Maybe it's a report from your SEO person with red and orange dots on it. Maybe it's a cold email warning you that your site is "failing Google's standards" and only their $2,000 fix can save you.
Here's what you actually need to know: Core Web Vitals are three measurements Google uses to grade how your website feels to a real person using it. Not how it looks. Not what it says. How it feels: does it show up fast, does it respond when tapped, does it hold still.
That's it. The names are intimidating, the ideas are not. By the end of this article you'll understand all three, you'll know how to check your own scores for free in two minutes, and you'll have a short list of questions that will tell you within one conversation whether a developer knows what they're doing. No technical background required.
Why Google Grades Your Site on Feel
First, the why, because it makes everything else make sense.
Google's business is sending people to search results they're happy with. People are reliably unhappy with pages that load slowly, freeze when tapped, or jump around mid-read. So Google built three standardized measurements of those exact frustrations, named them Core Web Vitals, and folded them into how it evaluates pages. The measurements come primarily from field data, meaning real Chrome users on your actual site, on their actual phones, in actual parking lots with two bars of signal. It's not a simulation. It's a report card written by your real visitors.
Two business takeaways before we get to the metrics themselves:
One: vitals are a real but modest ranking factor. Good vitals won't outrank better content and a stronger reputation. Bad vitals can hold an otherwise solid site back, more like a parking brake left on than an engine upgrade. Anyone who tells you Core Web Vitals are the secret to ranking #1 is selling something.
Two: the customer cost is bigger than the ranking cost. These metrics measure the experience of the person you already paid to attract, through ads, SEO, referrals, truck wraps, all of it. When the vitals are bad, some of those people leave before your page finishes loading. That loss never shows up on any report, and it's usually the bigger number.
The Three Metrics, Translated
LCP: "Is Anything Happening?"
Largest Contentful Paint measures how long it takes for the main content of your page, the biggest image or block of text, to actually appear on screen. Not the background color. Not a spinner. The thing the visitor came to see.
What it feels like when it's bad: you tap a link and stare at a blank or half-drawn screen, wondering if the site is broken or your signal dropped. Every one of those moments is a coin flip on whether the visitor stays.
Google's guideline: main content visible within 2.5 seconds counts as good. Over 4 seconds is officially poor, though honestly, it felt poor to your customer well before the label kicked in.
What usually causes bad LCP: giant unoptimized photos (the #1 culprit on small business sites), slow hosting, and bloated page builders that make the browser chew through a pile of code before showing anything. We went deep on all three in our site speed guide.
INP: "Is It Frozen?"
Interaction to Next Paint measures how quickly your page responds when someone interacts with it: taps the menu, hits a button, types in a form field. It asks, across the whole visit, whether the page reacted promptly or hung.
What it feels like when it's bad: you tap the hamburger menu and nothing happens. You tap again. Suddenly the menu opens and closes in one spasm. Or you hit "Submit" on a quote form and the button just sits there, so you hit it again and wonder if you requested two quotes or zero. That dead, unresponsive feeling is exactly what INP measures.
Google's guideline: responses within 200 milliseconds feel instant and count as good. (INP replaced an older metric called FID in 2024; if a report you're reading still talks about FID, it's outdated, which itself tells you something about who prepared it.)
What usually causes bad INP: too much JavaScript, the code that powers widgets, popups, chat bubbles, trackers, and builder features, all competing for the phone's attention at once. Budget phones feel this far worse than the latest iPhone your designer tested on.
CLS: "Why Did the Page Just Move?"
Cumulative Layout Shift measures how much your page jumps around while loading. Not speed at all, but stability.
What it feels like when it's bad: you start reading a paragraph and an image loads above it, shoving the text down. You go to tap "Get a Quote" and an ad or banner pops in at the last instant, so you tap something else entirely. Everyone has done the angry mis-tap. CLS is the angry mis-tap, quantified.
Google's guideline: a score of 0.1 or less is good. The units don't matter for your purposes. Low is stable, high is jumpy.
What usually causes bad CLS: images placed without reserved space, fonts that swap and reflow the text, and banners or embeds that inject themselves after the page starts rendering. It's almost always a sloppiness problem, not a hard engineering problem.
If you want to go deeper on any of the three, Google's own plain-language explainers at web.dev are genuinely readable and free.
Check Your Own Scores in Two Minutes
You do not need to pay anyone for this, and you definitely shouldn't pay anyone who acts like the numbers are secret knowledge.
Go to PageSpeed Insights and enter your homepage address. Two minutes later you'll have everything an auditor would charge you for:
- Look at Mobile first. It's the default tab for a reason. Most of your visitors are on phones, and mobile scores are always the weaker ones.
- The top section is the real-user data. If your site gets enough traffic, you'll see whether actual visitors are experiencing good, needs-improvement, or poor LCP, INP, and CLS over the past 28 days. This is the section Google actually uses, and it's the one that matters. Low-traffic sites may not have this data, and that's normal.
- The bottom section is a lab simulation with a 0-100 score and a diagnosis list. Treat it as the mechanic's inspection sheet: useful for finding what to fix, not a grade carved in stone. The lab score bounces around from run to run; don't let anyone alarm you with a single bad screenshot of it.
While you're in there, test your highest-value pages too, not just the homepage: your main service page, your contact page, whatever your ads point at. And test two competitors. Context turns a number into a decision.
One warning: do not fall down the rabbit hole of chasing a perfect 100 lab score. Passing all three vitals with real-user data is the meaningful finish line. Past that, your next dollar is better spent on reviews, content, and answering your phone, the things that actually win local customers, alongside solid local SEO.
What to Ask Your Developer (and What the Answers Tell You)
You don't need to become technical. You need three questions and an ear for confidence versus hand-waving.
"Do we pass Core Web Vitals on mobile, with field data?" A pro answers with specifics: which metrics pass, which don't, and what the field data shows versus the lab. Hand-waving, subject-changing, or "scores don't really matter" means keep asking. (Scores aren't everything, but a professional should still know yours.)
"What's our biggest problem, and what would fixing it cost?" A good answer names a specific culprit, usually images, a bloated theme or builder, excess scripts, or hosting, with a roughly sized fix. Be wary of anyone who quotes a big number before they've named the actual problem, and equally wary of "we just need a faster-website plugin." Plugins that promise speed often add the very bloat that causes the problem.
"Was the site built fast, or are we patching it after the fact?" This is the question that separates philosophies. Some sites are slow because of a few fixable mistakes. Others are slow structurally, because the platform and theme generate bloat faster than anyone can strip it out. An honest developer will tell you which yours is. If it's structural, ongoing "optimization" retainers are paying someone to bail a leaking boat, and at some point a rebuild on a lean foundation is the cheaper path. Our take on that decision is in the rebuild-or-redesign post.
If you're hiring someone new, ask one more: "Show me three of your live sites and let's run them through PageSpeed together, right now." Anyone who builds fast sites will love this request. Anyone who stalls just answered your real question. It works whether you run a plumbing company or a trucking operation; the bar doesn't change by industry.
The Honest Summary
Core Web Vitals are Google measuring three feelings: "is anything happening" (LCP), "is it frozen" (INP), and "why did the page move" (CLS). You can check your own grades free at PageSpeed Insights in two minutes. Passing matters, both as a modest ranking signal and, more importantly, as proof your site isn't quietly bleeding the visitors you paid to attract. Perfection past passing is a hobby.
And if a stranger emails you claiming your vitals are failing, now you can check in two minutes whether they're telling the truth. Usually that's the cheapest audit you'll ever run.
If You'd Rather Just Pass and Move On
This is what we do. We build done-with-you websites live on a call with you: first draft in 24 hours, live in 7 days, guaranteed. Every site we ship loads in under a second, which means the vitals conversation is over before it starts, and you can verify it yourself in PageSpeed Insights, the same way you'd check anyone.
Hosting, SSL, and outage monitoring included from $100 a month. Build tiers start at $500, with pay-in-4 or Klarna available. Veteran-owned, Wilmington, NC. 1,500+ small business sites built in the last 90 days.