Core Web Vitals for Wichita businesses, explained

Google grades every website on three measurements it calls Core Web Vitals. Most owners have never heard of them, most local sites fail them, and nobody sends you a notice when you do.

They're worth ten minutes of your attention because they decide two things at once: where you rank, and whether a customer is still there when your page finally appears. Here's what each one means in plain English, how to check yours free, and what actually fixes them.

The three numbers

That's the whole list. Three things, each measuring a different way a page can feel broken.

• LCP, Largest Contentful Paint: how long until the main thing on the page shows up. Google wants under 2.5 seconds. Plenty of local sites sit at 7, 10, or worse.
• INP, Interaction to Next Paint: how quickly the page reacts when someone taps or clicks. Under 200 milliseconds is good. This is the one behind a button that seems dead for a beat, so people tap it again and sometimes submit twice.
• CLS, Cumulative Layout Shift: whether the page jumps around while loading. Under 0.1 is good. If a customer goes to tap 'call' and an image loads above it, shoving the button down as their thumb comes in, that's this one, and it's the most infuriating of the three.

Notice what they have in common. None of them measure how pretty your site is or how well written it is. They measure whether using it is a pleasant experience on a phone, which is exactly what a visitor is deciding in the first few seconds.

It's also worth knowing that these are graded as pass or fail rather than on a curve. Google looks at what most of your real visitors experience, not your best-case load on fast wifi, so a site that's quick for some people and slow for the rest still fails. That surprises owners who tested it once from the office and concluded everything was fine.

Why they matter twice

First, Google uses them as a ranking signal. All else being equal, a site that passes is favored over one that fails, and in a local market where several businesses offer similar things, all else is frequently close to equal.

Second, and more important, real people feel them whether or not Google exists. Someone standing in a parking lot on mobile data decides in about three seconds. If your main content still hasn't rendered, they're already back on the results page tapping the next business. You never learn this happened. There's no bounce notification, no angry email. The call simply doesn't come.

That's what makes this worth caring about even if you don't care about SEO at all. It's not an abstract score, it's the experience every customer has before deciding whether you're worth their time.

What failing actually looks like

I audited a local site recently where the main content took more than eleven seconds to appear, with over six seconds spent just waiting for the server to respond at all. Six seconds before the browser had anything to work with.

That business is paying, through ads, through search, through word of mouth, to get every one of those visitors there, and losing most of them before the page becomes usable. And it isn't the owner's fault. They were sold a heavy template-built site, told it was fine, and had no reason to know otherwise. It looked perfectly good on the laptop where they reviewed it.

That's the trap with all of this. Your own site always feels fast to you, because your browser cached it, you're on good wifi, and you know exactly where everything is. You are the least reliable judge of your own site's speed.

What passing looks like

Cloud 9 Slime is my clearest before-and-after. The old site scored 35 out of 100 on performance, 52 on accessibility, 61 on best practices, and 48 on SEO. Four failing grades on a store that looked completely fine to its owners.

The hand-built rebuild scores 92 on performance, 97 on accessibility, 96 on best practices, and a perfect 100 on SEO. Same business, same products, same photographs of the same slime. The only thing that changed was what the browser had to do before the page appeared.

Rush Fire Protection, 3 Keys & Co, and F3 Wichita all score a perfect 100 on mobile and desktop. Those are live sites you can test yourself in about thirty seconds, which is the point of naming them.

How to check yours in two minutes

Open PageSpeed Insights, paste your URL, and read the mobile tab. Not desktop. Desktop scores flatter everyone because a laptop on office wifi is nothing like a phone on cellular in a parking lot, and your customers are in the parking lot.

Two things to understand in the results. The top section shows real data from actual Chrome users on your site, when Google has enough of it, and that's the version that affects rankings. Below it is a lab test run on a simulated device, which is useful for diagnosing but isn't what Google scores you on.

Then run the same test on your two closest competitors. That comparison matters more than the absolute number, because you're not trying to beat a universal standard, you're trying to beat the other businesses in your local results.

What actually fixes them

Honest answer first: some of this is tuning and some of it is structural, and knowing which you're facing saves a lot of wasted effort.

The tuning side is real and worth doing. Oversized images are the single most common cause of bad LCP on small-business sites, and properly compressed, correctly sized images often produce a large improvement on their own. Specifying image dimensions in the code fixes most CLS problems, because the browser reserves the space before the picture arrives instead of shoving everything down when it does. Removing plugins and third-party scripts you don't need helps INP, since chat widgets, tracking pixels, and analytics tools all compete for the same thread that's supposed to respond to taps.

The structural side is where tuning runs out. If the page arrives as a set of instructions the browser has to execute before anything displays, you're fighting the architecture. The reason my builds score where they do is that every page is generated ahead of time as finished HTML, so it arrives ready to paint. That's a decision made at the start, not a fix applied at the end, which is why some sites can be tuned and others genuinely need rebuilding.

How much do they really affect rankings?

Worth being straight about this, because the SEO industry oversells it in both directions. Core Web Vitals are a genuine ranking signal, but they're a tiebreaker rather than the main event. A fast page about the wrong thing will not outrank a slower page that actually answers the question.

So if you're invisible in search, speed alone won't rescue you. Relevance comes first: does your site plainly say what you do and where you do it. Speed decides the close calls, and in local search a great many calls are close, because you and three competitors all offer roughly the same service in roughly the same city.

But here's why I'd fix speed even if Google ignored it entirely. The ranking effect is a bonus. The real return is that the visitors you already earn actually stay long enough to read something. You're not optimizing for an algorithm, you're removing a barrier between a ready customer and your phone number, and that barrier costs you whether or not anyone is watching.

What to do this week

Run the test on mobile. Run it on two competitors. If you're in the red and they're in the green, you now know something specific about why their phone rings more than yours, and it has nothing to do with who does better work.

Then start with images, since it's the highest-impact thing most owners can do without touching the platform. If that doesn't move it much, the problem is structural and no amount of tweaking will get you there.

One last note on expectations. Because the real-world portion of the score is built from actual visitor data collected over time, improvements don't register the same day you make them. The experience gets better immediately for every person who lands on your site, but the reported number lags by weeks. Don't fix something on Monday, retest on Tuesday, and conclude it didn't work.

Want your real numbers explained? Send me your URL and I'll audit it and tell you exactly what's dragging it down and whether it's a tuning job or a rebuild. No charge, and I'll tell you if it's already fine.

Frequently asked questions