People leave slow websites. On a phone, with an average mobile connection, a page that takes too long to appear loses visitors before they have seen a single thing you offer. Google also pays attention to how quickly a page becomes usable, so a slow site can hurt your search ranking too.
The good news is that most slow sites are slow for the same handful of reasons, and most of them are fixable.
Check yours first (two minutes, free)
Open Google's PageSpeed Insights, paste in your address, and run the mobile test. Look at the score, but pay more attention to the list of opportunities underneath. That list tells you what to fix first.
The usual suspects
1. Huge images. The number one cause. A photo straight from a phone can be several megabytes. Resize images to the size they are actually shown, use modern formats like WebP, and load images below the fold only when the visitor scrolls to them.
2. Too many plugins and scripts. On WordPress especially, every plugin adds code to every page. Chat widgets, tracking pixels, sliders and social feeds add up. Remove what you do not use and question what you do.
3. No caching. Without caching, your server rebuilds the same page from scratch for every visitor. A caching layer saves a ready-made copy and serves it instantly. On the sites I run, this alone makes a clear difference.
4. Slow or overloaded hosting. If your site shares a crowded server, or sits far from your visitors, everything feels slow no matter how well it is built. A CDN such as Cloudflare serves your files from locations closer to your visitors.
5. Heavy page builders and themes. Some themes load large amounts of code for features you never use. A lean, purpose-built theme is faster than a multipurpose one.
6. Slow database queries. On custom apps, one badly written query can slow a whole page. This one is invisible to the eye but easy to spot for a developer with the right tools.
7. Third-party code you cannot control. Fonts, embedded videos and ad scripts load from other companies' servers. Keep only what earns its place.
What fixes it, in order of impact
- Compress and resize images.
- Turn on caching and a CDN.
- Remove unused plugins and scripts.
- Move large files, such as your media library, to dedicated storage. On one of the sites I manage, uploads go to Cloudflare R2 and load from the CDN, which keeps the server light.
- Review the database and code if the site is custom-built.
Often the first three fixes get you most of the improvement, and they do not require rebuilding anything.
When to call someone
If you have done the basics and the score is still poor, or the site is a custom app that slows down as it grows, it is worth getting a proper audit. A developer can find the one or two real bottlenecks instead of you guessing.
That is a service I offer: I look at your site, tell you what is holding it back, and fix it without breaking what already works. Send me your address and I will tell you what I see.