A slow website costs you customers and rankings before anyone reads a word: as load time climbs past a few seconds, conversions drop and Google quietly demotes the page. The targets that matter are simple — Largest Contentful Paint under 2.5 seconds, interaction response under 200 milliseconds, and almost no layout shift. Hit those and speed stops being the thing costing you sales. Miss them and you're paying for traffic that leaves before it ever converts.
Why does speed change conversions?
Speed is the first impression, formed before a visitor reads a single word. Every extra second of load raises the share of people who leave before the page even appears, and the ones who stay trust a sluggish site less. On mobile — where most of your traffic now is, often on a patchy connection — a slow page is frequently the difference between a lead and a bounce. There's a plain psychology to it: fast feels professional and in control; slow feels broken and risky, and risk doesn't convert. The cruel part is that you've already paid to get that visitor — through ads, SEO, or word of mouth — so a slow page wastes the money you spent to attract them, on top of the sale you never make.
What targets should you hit?
Google measures three Core Web Vitals on real users — field data from real devices and networks, not a lab test on your fast laptop:
- LCP (largest contentful paint): load the main content in under 2.5 seconds.
- INP (interaction to next paint): respond to taps and clicks in under 200 ms.
- CLS (cumulative layout shift): keep the layout from jumping, under 0.1.
Because these are measured on the people actually using the site, the only test that counts is how it performs for them, not for you on a good connection. And fix the server first — a slow server makes every page slow no matter what you optimize on top of it.
How much does slow actually cost?
More than most owners realize, because the loss is invisible — you never see the visitors who left. The cost shows up three ways: fewer conversions from the same traffic, lower Google rankings (which means less traffic in the first place), and weaker trust that drags on everything from sign-ups to sales. None of it appears as a line item; it's just a revenue number that's quietly lower than it should be. That's what makes speed easy to ignore and expensive to neglect — the bill arrives as growth you simply never got, and you can't miss what you never saw.
What actually makes a site slow?
Usually a few ordinary culprits: heavy unoptimized images (the number-one offender by far), bloated page builders and plugin stacks, render-blocking scripts and third-party tags, and a slow or overloaded host. Most slow small-business sites are slow for boring, fixable reasons — not exotic ones — which means a full rebuild often isn't needed; disciplined cleanup gets them back in range. The genuinely hard cases are bloated templates where the slowness is baked into the foundation: every page inherits the weight, and no amount of tuning fully escapes it. Those are the ones I usually recommend rebuilding on a lean stack rather than patching forever.
How do you measure your site's speed?
Two free tools cover it. Google's PageSpeed Insights scores a single URL with both lab and real-user field data, then lists specific fixes ranked by impact — start there. For ongoing monitoring, the Core Web Vitals report in Google Search Console tracks LCP, INP, and CLS across your whole site over time using real visitor data, so you catch regressions after you ship something heavy. Test on an actual mid-range phone on mobile data too, not only the desktop preview — the gap between a fast laptop and a real phone is exactly where most sites quietly fail. Measure before and after every change, or you're optimizing blind.
How do I keep sites fast?
I build on a modern server-rendered stack — Next.js on Vercel — with compressed, correctly sized images, minimal scripts, and the content in the initial HTML so it appears immediately. Speed is a build decision, not a plugin you bolt on later: a site that's fast by architecture stays fast, while a slow one patched after launch tends to drift back. It's the same websites service behind real launches like Little Chubby Press, where fast is the default, not an upgrade you pay extra for. I also keep it fast as it grows — performance is a budget you defend over time, which I cover in how to keep your website fast.
Related growth guides
Pair this with SEO basics every founder should own and 7 signs your website needs a rebuild.
Is a slow site costing you leads? Send me your URL — I'll tell you what's dragging it down.
