Core Web Vitals, explained for non-engineers

If you’ve ever opened a site-speed report, you’ve been hit with acronyms: LCP, INP, CLS. These are Google’s Core Web Vitals, three metrics it uses to measure how a real person experiences your page loading. They feed into search rankings, and they show up in tools like PageSpeed Insights and Search Console. You don’t need to be an engineer to understand them, and understanding them helps you tell whether the people building your site are doing it well.

Here’s each one in plain English.

LCP, how fast the main thing shows up

Largest Contentful Paint measures how long it takes for the biggest, most important piece of content to appear, usually your hero image or headline. It’s the answer to “how long until the page looks like it’s loaded?”

• Good: under 2.5 seconds.
• Common causes of a bad score: huge unoptimized images, slow hosting, render-blocking scripts, or fonts that delay the text appearing.

LCP is the one your visitors feel most directly. A bad LCP is the “is this thing even loading?” experience.

INP, how fast the page responds when you touch it

Interaction to Next Paint measures responsiveness: when someone taps a button or opens a menu, how long until the page visibly reacts? A page can look loaded but still be unresponsive because it’s busy running JavaScript in the background. INP catches that gap.

• Good: under 200 milliseconds.
• Common cause of a bad score: too much JavaScript executing, so the browser is too busy to respond to taps. (This is one more reason we ship as little JavaScript as possible.)

INP is the “I tapped it twice because nothing happened the first time” experience.

CLS, whether the page jumps around as it loads

Cumulative Layout Shift measures visual stability: does content jump around while the page loads? You’ve felt bad CLS when you go to tap a button and an ad or image loads above it, shoving everything down, and you tap the wrong thing.

• Good: under 0.1.
• Common causes: images without dimensions set, ads or embeds that load late, or fonts that swap and reflow the text.

CLS is the “the page moved right as I went to click” experience, small, but genuinely infuriating.

What to do with this

You don’t have to fix these yourself, but you should know three things:

1. You can check your own site for free. Run it through Google’s PageSpeed Insights. It grades all three on real-world data and tells you specifically what’s hurting each one.

2. Green across the board is achievable. These aren’t aspirational targets. A well-built site hits all three comfortably. If your site is in the red, that’s a sign of how it was built, not an unavoidable fact of the web.

3. The fixes are usually structural, not cosmetic. Bad scores typically trace back to a heavy page builder, an overloaded theme, too many third-party scripts, or a framework doing far more than the site needs. Patching individual metrics rarely sticks; building lean from the start does.

If your Core Web Vitals are in the red, it’s worth understanding why before you spend money on plugins promising to fix it. Usually the honest answer is that the foundation is the problem. We build sites that pass these by default, not because we optimize hard at the end, but because we don’t add the weight in the first place. Want a second opinion on yours?