More than half the people who open a website on their phone leave if it takes longer than three seconds to load. They don’t wait and they don’t come back: they move on to the next one. When your website is slow it isn’t just an annoyance for your visitors, it’s money walking out of the door before anyone gets to see what you offer. And the good news is that it can almost always be fixed.
What a «slow» website really means and how Google measures it
«Slow» is a feeling, but Google has turned it into hard numbers. Since 2021 it has used three measurements, the Core Web Vitals, to work out how fast and stable a website feels to a real person. They don’t measure how long all the code takes to load, but what the visitor actually notices: how long they wait to see something, how quickly the page reacts and whether the content shifts under their thumb while it loads.
The rush is sharper on mobile, and in Spain mobile rules: according to Flat101’s study of conversion in digital businesses, 66% of web traffic now comes from phones. That’s exactly where the connection is patchiest and patience shortest, so a website that «works fine» on a desktop may be losing customers in people’s pockets without you ever noticing.
| Measurement | What it measures | Good | Poor |
|---|---|---|---|
| LCP (loading) | How long the main content of the page takes to appear | ≤ 2.5s | > 4s |
| INP (responsiveness) | How long the site takes to react when you tap or click | ≤ 200ms | > 500ms |
| CLS (stability) | How much the content moves while the page finishes loading | ≤ 0.1 | > 0.25 |
These three measurements aren’t a passing fad: INP replaced the previous metric in March 2024, and today they’re part of how Google decides who to place higher. They aren’t everything, but when two websites compete for the same search and one loads fast while the other doesn’t, that’s a nudge you don’t want to hand over for free.
Test it yourself in two minutes
Go to PageSpeed Insights (pagespeed.web.dev), type in your website’s address and choose «Mobile». It will give you a score and, more usefully, the real timing for each measurement. If you have access to Search Console, its «Core Web Vitals» report tells you how your pages are doing with data from actual visitors, which is what counts for Google. Bear one thing in mind: the one-click PageSpeed score is a lab test, a rough guide; what really matters for ranking is the data from your real visitors, which takes a few weeks to build up.
Why your website is slow: the most common causes
On the websites we review, slowness almost never comes from a single thing, but from several small ones adding up. One huge image here, one plugin too many there, a chat widget that loads before the content itself, and the result is a website that takes three times longer than it should. The good news is that, for that very reason, fixing three or four things is usually enough to notice a big difference. These are the causes we see most, roughly in order of how much they weigh:
- Unoptimised images. This is, by far, the number one cause. Photos of several megabytes uploaded straight from a phone or camera, then shown in a slot ten times smaller. The browser downloads the full-size photo anyway.
- Hosting that’s too cheap. If the server is slow to respond, the website starts late no matter what. It’s the ceiling you can’t see: no optimisation trick fixes it completely.
- Too many plugins. Each plugin adds its own code to load. Ten well-chosen plugins are no problem; thirty half-used ones are.
- No caching system. Without caching, the website is rebuilt from scratch on every visit instead of serving a ready-made version. It’s one of the biggest wins for the least effort.
- Heavy themes and page builders. Many websites built with visual builders drag along mountains of CSS and JavaScript the page never actually uses, but which the browser downloads all the same.
- Blocking third-party scripts. Chats, advertising pixels, maps, embedded videos and external fonts hold up that first load while the visitor stares at a blank screen.
- No CDN. If every file comes from a single server and the visitor is far away, each image and each file takes longer to arrive.
To show what’s at stake, here is Google’s data on how many people leave depending on how long your website takes, compared with one that loads in a single second:

Speed doesn’t only affect people who are already on your website. A slow site also pushes up the cost of your ads, because Google Ads rewards fast-loading pages with a better price, and it makes it harder to show up on Google when the crawler takes longer to work through your pages. It’s a problem you pay for on every front at once.
Is your website slow and you don’t know where to start?Work out in a minute what it would cost to tune it up or rebuild it so it flies.
How to find out what’s slowing yours down
Before fixing anything it pays to know where the bottleneck is, because each symptom points to a different place. With the loading time in front of you and a look at how the page behaves, the diagnosis almost makes itself:
| What you notice | Where the problem is | What to do |
|---|---|---|
| It’s slow to appear the first time, even when nearly empty | Server and hosting | Better hosting, server-side caching |
| Images appear bit by bit, from top to bottom | Heavy images | Compress, modern format, correct size, lazy loading |
| Fine on a desktop, but it drags on mobile | Too much code | Remove scripts and styles that aren’t used |
| The content jumps and shifts while it loads | Stability (CLS) | Reserve the space for images and ads before they load |
| Slow to respond when you tap a button or a menu | Responsiveness (INP) | Lighten the JavaScript that runs on load |
What to fix first so it loads fast
With the diagnosis done, the order matters as much as the what. Our rule is to start with what gives the most improvement for the least effort and leave for last the things that mean touching the foundations. This is the path we follow:
- Measure it before touching anything. Note the mobile loading time of your most important pages. Without that starting point you won’t know whether what you do makes things better or worse.
- Fix the images. It’s what pays off most. Compress them, switch them to a modern format like WebP, serve them at the size they’re shown and let the ones further down load only when the visitor reaches them.
- Add a proper caching system. This way the website serves a ready-made version instead of rebuilding itself on every visit. It’s the biggest gain for the least work.
- Remove what you don’t use. Half-used plugins, scripts for services you no longer have and surplus fonts. Fewer pieces, less to load.
- Review the hosting. If, after all of the above, the server is still slow to respond, it’s time to move to better hosting. It’s the base everything else rests on, and moving from a saturated shared host to a decent one often halves the response time.
- Measure again. Compare with the starting point and go over whatever is still weak. Speed is maintained, not fixed once and forgotten.
When it’s done properly, the change shows in several places at once:
- More people stay. The visits that used to leave in the first second now get to see what you offer.
- Better position on Google. All else being equal, the fast website overtakes the slow one.
- More sales and more enquiries. Every tenth of a second counts, especially in an online shop.
- Cheaper ads. Google rewards fast pages with a better cost per click.
Fix it or rebuild the website?
Patching isn’t always worth it. If the website is old or built on a base that drags along code you can’t clean up, there comes a point where every speed improvement breaks something else. This is how we tell one case from the other:
| A fix is enough | Time to rebuild |
|---|---|
| It loads reasonably and only falls down on images or missing caching | It’s built with a page builder that drags along code you can’t remove |
| The design works for you and turns visits into customers | Every time you speed up one part, another breaks |
| The problems are isolated and specific | It’s old, insecure or nobody can maintain it any more |
If the website is old and slow in equal measure, a new one, designed from the start to load fast, often works out better than carrying on with sticking plasters. We see this often when traffic has dropped as well and several problems pile up at once. (For now, our in-depth piece on traffic drops is only in Spanish; you’ll find more on our insights page.)
What you can do today
Open pagespeed.web.dev, type in your website’s address, choose «Mobile» and look at two things: the score at the top and the LCP time. That alone tells you whether your website is good, average or poor, and puts the list of what to fix first right in front of you. It won’t take more than two minutes.
If your website is slow and losing visitors, or the time has come to rebuild it so it loads fast and converts, we can help. Take a look at our web design service or tell us what’s going on with yours and we’ll take a look.



