Guide · 22 July 2026
Slow website: why it costs you customers and how to fix it
A slow site loses visitors before it shows anything, and Google penalises it. The good news: it's almost always fixed with configuration, not a rebuild.
Why speed matters more than it seems
A site's speed isn't a technical vanity metric: it's the first impression. Someone arriving from a search or an ad decides within seconds whether to stay, and if the page is still blank those seconds are gone. Every extra second of waiting raises the share of people who leave. It's a measured, consistent effect, stronger on phones, where most visitors are. On top of that, since 2021 Google uses speed as a ranking factor through the Core Web Vitals: a slow site starts at a disadvantage in results too.
The most common causes (in order of frequency)
- Oversized images. The number one cause. Photos served at full resolution, uncompressed and in dated formats: the visitor downloads pointless megabytes. Compression is invisible to the eye but shows up in the timings.
- An overloaded budget host. If the server is slow just to respond, everything else starts late. It's the starting line for every other timing.
- Too many plugins and external scripts. Chat widgets, maps, embedded videos, tracking: each one adds weight, often more than your own site.
- Files that block the first screen. CSS and JavaScript that must fully download before anything appears. Fixed by loading them in a deferred way.
- No caching or compression. Two server settings that, once on, make repeat visits nearly instant.
How to fix it, without starting over
The most useful move is to start from data, not a hunch. A serious speed test tells you not just how slow you are, but why, and which fixes win back the most time. From there you work in order of impact: usually images first, then compression and caching, then third-party scripts to defer or remove. These are jobs of hours, which whoever manages the site can do without touching its foundations.
Start here: run the free speed test on your site. It measures with Google's engine and real Chrome user data, explains every problem in plain language, and orders the fixes by impact. The report copies with one click to hand to whoever runs the site.
While you're at it, a fast site is little use if AI can't read it: see also how to get found by ChatGPT and AI Overviews.
Frequently asked questions
›How fast should a website load?
The most common benchmark is Largest Contentful Paint, the time to show the main content: under 2.5 seconds is good, over 4 seconds is slow. But the number that really matters is the one measured on real mobile users, where connections are slower.
›Why is my website slow?
The most common causes are oversized images, an overloaded budget host, too many plugins or third-party scripts (chat, maps, tracking), and files that block the first screen. It's almost always several problems at once, and the ones to fix first are those with the biggest impact on load time.
›Does speed matter for Google?
Yes. Speed (through the Core Web Vitals) is a ranking factor, especially on mobile. But the most immediate effect is on visitors: every extra second of waiting raises the share of people who leave before the page appears.
›Do I need to rebuild my site to speed it up?
Almost never. Most of the gains come from configuration: compressing images, enabling text compression and caching, deferring non-essential scripts. That's hours of work, not a rebuild, unless the site is built on very heavy foundations.