“Is my website fast?” sounds like it should have a yes/no answer. Instead, the industry answers with acronym soup — LCP, INP, CLS, Core Web Vitals — and most business owners reasonably tune out. That’s a shame, because behind the acronyms are three completely intuitive questions, and the answers show up in your revenue.

Here’s the whole topic, translated.

The three questions Google asks about your site

Google measures how real Chrome users experience your pages — not a lab test, actual visitors — and boils it down to three numbers. Each is just a human annoyance, quantified:

LCP — “How long until I see the thing I came for?” Largest Contentful Paint: the time until the main content — hero image, headline — is on screen. Target: under 2.5 seconds; genuinely good sites do it in under 1. Every slow second here is customers deciding your business feels as sluggish as your website.

INP — “When I tap something, does it respond?” Interaction to Next Paint: the delay between a tap or click and the page visibly reacting. Target: under 200 milliseconds. INP replaced an older, more forgiving metric precisely because sites had learned to load fast but still felt janky to use — usually from JavaScript bloat chewing the phone’s CPU. If your site was built on a heavy platform, this is the number quietly hurting you.

CLS — “Did the page jump around and make me tap the wrong thing?” Cumulative Layout Shift: how much content moves after it appears. You know this one personally — the button that dodges your thumb because an ad loaded above it. Target: near zero.

Why this is a business metric, not a nerd metric

Two mechanisms turn these numbers into money:

Ranking. Core Web Vitals are a Google ranking signal. Modest, not dominant — but in a tight race for page one, the faster site gets the tiebreak. And as clicks get scarcer in the AI-answer era, tiebreaks matter more.

Conversion. This one’s bigger. The relationship between speed and completed actions — purchases, quote requests, calls — is one of the most consistently replicated findings in e-commerce: every additional second of load time measurably increases abandonment. Visitors on a phone, on cellular, mid-errand, do not wait around. Your marketing budget buys the visit; speed decides whether the visit becomes a customer.

How to check your own site (free, two minutes)

Go to PageSpeed Insights (pagespeed.web.dev), enter your URL, and look at the field data at the top — that’s real users. Check the phone tab, not desktop; that’s where your customers are. Green across LCP, INP, and CLS: you’re solid. Orange or red: you now know exactly what’s costing you.

Why some sites are effortlessly fast

Here’s the part vendors don’t advertise: these scores are mostly determined by architecture, not optimization effort. A site that’s pre-built into static files and served from an edge network starts with a near-perfect scorecard because there’s simply nothing slow in the pipeline — no database query, no server assembling pages, no megabytes of platform JavaScript. A heavyweight page-builder site starts in a hole that no amount of plugin-tuning fully escapes.

It’s why every site we build is static-first: we’d rather be fast by construction than fast by heroics.

Run your numbers. If the phone tab came back orange or red — or you’d just like the green explained — send us the URL and we’ll tell you what it would take. Straight answer, as always.