Why Your Website Speed Is Losing You Customers (And How to Fix It)
A one-second delay in page load time can reduce conversions by 7%. Learn why speed matters more than ever in 2024, what's slowing your site down, and the concrete steps to fix it.
The Silent Revenue Killer
Your website can look stunning — beautiful photography, polished copy, a clear call to action — and still be bleeding customers every single day. The culprit? Speed. Or rather, the lack of it.
Google's data shows that as page load time goes from one second to three seconds, the probability of bounce increases by 32%. Go from one second to five seconds, and that number jumps to 90%. These aren't edge cases or technical edge users. These are your real customers, on their real phones, deciding in milliseconds whether your business is worth their time.
What Google Actually Measures
Since 2021, Google has used Core Web Vitals as a direct ranking factor. There are three key metrics you need to understand:
- LCP (Largest Contentful Paint): How quickly does the main content of your page appear? Google's target is under 2.5 seconds.
- FID / INP (Interaction to Next Paint): How quickly does your page respond to user interactions like clicks and taps? Target is under 200ms.
- CLS (Cumulative Layout Shift): Does your page jump around as it loads, accidentally making users click the wrong thing? Target is a score below 0.1.
The uncomfortable truth: most small business websites fail all three. Not because the businesses are bad — but because the developer who built them never thought about performance.
The Most Common Culprits
After auditing dozens of websites, the same issues appear over and over again. Unoptimised images are the number one offender. A product photo taken on a modern camera can be 6–12 MB. Properly compressed and formatted as WebP, the same image should be under 200 KB. Here's how to convert an image in the terminal:
# Convert a PNG to WebP with quality 80 using cwebp
cwebp -q 80 photo.png -o photo.webp
# Or use ImageMagick to resize AND convert
magick photo.jpg -resize 1200x -quality 80 photo.webpRender-blocking JavaScript is when scripts are loaded synchronously in the <head>, preventing the browser from rendering anything until the script has downloaded and executed. The fix is simple:
<!-- ❌ Blocks rendering — loads synchronously -->
<script src="/analytics.js"></script>
<!-- ✅ Deferred — doesn't block rendering -->
<script src="/analytics.js" defer></script>
<!-- ✅ Async — also non-blocking, fires as soon as downloaded -->
<script src="/third-party-widget.js" async></script>No caching strategy means every visitor downloads everything from scratch, every time. Here's a production-ready Nginx cache configuration:
# Cache static assets for 1 year
location ~* \.(jpg|jpeg|png|gif|webp|svg|ico|woff2)$ {
expires 1y;
add_header Cache-Control "public, immutable";
}
# Cache CSS/JS for 1 year (use content hashes in filenames!)
location ~* \.(css|js)$ {
expires 1y;
add_header Cache-Control "public, immutable";
}
# Never cache HTML — always serve fresh
location ~* \.html$ {
expires -1;
add_header Cache-Control "no-cache, no-store, must-revalidate";
}The Business Impact Is Real
Walmart ran a study showing that every 1 second of improvement in load time resulted in a 2% increase in conversions. Amazon estimated that a 100 ms delay cost them 1% in sales. Even for a small business doing €50,000 a year in online revenue, a 2% conversion improvement is €1,000 — more than enough to justify a proper performance audit.
What You Can Do Right Now
Run your site through Google PageSpeed Insights (pagespeed.web.dev) and look at your score for both mobile and desktop. If your mobile score is below 70, you have a problem worth addressing. Below 50, it's urgent.
Then look at the "Opportunities" section. PageSpeed will tell you specifically which images aren't optimised, which scripts are render-blocking, and what the estimated time savings would be for each fix.
Performance Is Not Optional
The web has matured. Users expect pages to load in under two seconds. Google rewards fast sites and penalises slow ones. And every second of delay is a direct hit to your revenue and your reputation.
When I build a website, performance isn't a feature I add at the end. It's a constraint I design around from the beginning. Images are sized correctly, JavaScript is loaded asynchronously, fonts are preloaded, caching is configured on day one. That's what separates a professional build from one that looks good in a screenshot but fails in the real world.
Ready to fix these issues on your site?
I build websites that are fast, SEO-optimised, and properly configured from day one. Let's talk about your project.
Start a conversation