Imagine a shop where the door takes four seconds to open. Some customers wait. Many glance at it, shrug, and walk to the shop next door whose door is already open. You’d never run a shop like that — but a slow website is exactly that door, and most businesses don’t realise theirs is sticking.
Speed feels like a technical detail, something for developers to worry about. It isn’t. It’s one of the most direct levers you have on how much money your website makes. Here’s why, with the numbers.
The data: milliseconds move money
This isn’t a hunch. Large studies have measured it repeatedly:
- Deloitte found that improving mobile load time by just 0.1 seconds lifted retail conversion rates by 8% and average order value noticeably too. A tenth of a second.
- Google’s own research showed that as page load goes from 1 second to 3 seconds, the probability a visitor bounces rises by 32%. From 1 to 5 seconds, it more than doubles.
- Amazon famously calculated that every 100 milliseconds of extra latency cost them about 1% in sales.
The pattern is consistent across industries: faster sites keep more of the people who arrive, and turn more of them into customers. Slowness is a silent, continuous leak in your funnel — one that never shows up as an angry email, because the people you lose simply left.
Why sites end up slow
Very few sites are slow on purpose. They get slow the way a garage gets cluttered — one thing at a time:
- Oversized images. A photo exported straight from a camera or a stock site can be several megabytes. Put a few on a page and it’s heavy before a single word loads.
- Too much script. Analytics, chat popups, marketing pixels, A/B-testing tools, social widgets — each one is code the browser must fetch and run before the page feels ready.
- Heavy platforms and themes. A general-purpose CMS with a “does-everything” theme and a stack of plugins ships a huge amount of code, most of which your particular page never uses.
- Render-blocking everything. When fonts, styles and scripts all have to load before anything appears, your visitor stares at a blank screen while the meter runs.
Individually, none of these feels like a problem. Together, they’re the four-second door.
Core Web Vitals, without the jargon
Google measures real-world speed with three numbers called Core Web Vitals. In plain English:
- LCP (Largest Contentful Paint) — how long until the main thing on the page (usually the big heading or image) actually shows up. Aim for under 2.5 seconds; the best sites are under 1.
- INP (Interaction to Next Paint) — when someone taps or clicks, how quickly the page responds. Sluggish, janky pages fail here.
- CLS (Cumulative Layout Shift) — whether things jump around as the page loads (the annoying moment you tap a button and it moves). Lower is better.
These aren’t just Google trivia — they feed into search rankings, and they closely track how fast the site feels to a real person. A site that passes them comfortably feels instant, and instant sites convert.
What “fast” actually looks like
Fast isn’t a vibe; it’s measurable. A genuinely fast small-business site loads its main content in under a second, scores 100/100 on Google’s Lighthouse performance check, and weighs a few hundred kilobytes rather than a few megabytes.
That’s not a theoretical target. The demo builds on this site — a bakery, a law firm and an electrician — each hit 100/100 performance with sub-second load times, at a fraction of the weight of a typical site. Same category of business you probably run; wildly different speed.
How to fix a slow site
The order matters. Do this:
- Measure first. Get real numbers before touching anything — Lighthouse, PageSpeed Insights, or the meter on our homepage, which shows your speed and carbon side by side against a fast benchmark. You can’t fix what you haven’t measured.
- Cut the images down. Resize to the size actually displayed, convert to modern formats, lazy-load anything below the fold. This alone often halves page weight.
- Remove scripts that don’t earn their keep. Every third-party tag should justify its cost in speed. Most sites are carrying tags no one even looks at any more.
- Question the platform. Sometimes the fastest fix isn’t tuning a heavy site — it’s rebuilding it lean. A static site ships only the code a page needs, which is why it starts fast and stays fast.
- Serve it from fast, efficient hosting. Where your site is served from affects how quickly bytes reach your visitor.
The Leavsy approach: fast by default
At Leavsy, speed isn’t an upsell or a phase-two optimisation — it’s the starting point. Sites are built as lightweight static pages (Astro) and served from fast, low-carbon hosting, so 100/100 performance and sub-second loads are the default, not a stretch goal. And because a fast site is also a light one, it’s greener too — the same work solves both. (More on that in How much CO₂ your website emits.)
If you want to know what your current site is costing you in lost speed, a free 24-hour audit will show you your real numbers and what a rebuild would change. And if you already want a site that’s quick out of the box, the pricing is published openly — starting at €500.
Your website has one job: turn visitors into enquiries. A slow one quietly fails at that job every day. Speed is how you stop the leak.