Why speed is money: Core Web Vitals without the tech talk

You've felt it a thousand times as a customer: a page that feels sluggish without being able to point at why. The button that only reacts on the second tap. The text that jumps right as you're about to tap it. That's not bad luck - it's measurable, and Google measures it.

The three numbers Google judges you on

• How fast does the page show its main content? Past 2.5 seconds, people start dropping off.
• How fast does the page react when you tap? Anything above a quarter of a second feels broken.
• Does the content jump around while the page loads? Every jump is a mis-tap and an irritation.

None of these are “tech for tech's sake”. They're three ways of measuring the same thing: does your site feel like quality, or does it feel like resistance?

What it means in money

The link between speed and conversion is one of the most replicated findings in e-commerce: every time load time grows, the share of visitors who complete a purchase drops. It's not that customers are impatient out of spite - it's that waiting reads as untrustworthiness. A slow site feels like a messy store.

Speed isn't a technical detail. It's the first impression, measured in milliseconds.

The three culprits I find most often

• Full-resolution images scaled down in the browser - never pay for pixels nobody sees
• JavaScript from plugins and trackers loading before the content - measure before you measure
• Fonts and banners shoving the page around while it builds itself

Test it yourself in two minutes

Open pagespeed.web.dev, paste in your most important page - not the homepage, but the page where customers actually buy - and look at the three numbers. Green across the board? Then speed isn't your problem right now. Yellow or red? Then you know where the leak is, and it can be found and closed. It's some of the most measurable work that exists in web development.