A slow WordPress site is expensive, even if it never shows up on an invoice. Mobile visitors do not wait: they go back to Google and click on a competitor. Moreover, speed is one of the signals Google takes into account when ranking pages.
The usual reflex is to install a caching plugin. However, caching often hides the problem without solving it. Here are the eight causes we see most often, and the real fix for each one.
Why a slow WordPress site loses customers
On a phone, every second of waiting increases the chance of leaving. Visitors coming from an ad are even less patient. So a slow page wastes part of your advertising budget before customers even see your offer.
1. A heavy all-in-one theme
Themes sold with dozens of demos often load scripts and styles that every page does not need. The fix: a lightweight theme, or a custom theme that only contains what your site actually uses.
2. Too many plugins
Every plugin adds code, queries and sometimes external files. So take stock: delete the ones you no longer use and replace three small plugins with one well-chosen tool.
3. Oversized images
A 4 MB photo taken on a phone has no place on a web page. Resize images to their display size, convert them to WebP and enable lazy loading. This is often the most dramatic gain.
4. A page builder used carelessly
Visual builders are handy, but every nested section adds code. For example, a simple About page can generate hundreds of useless tags. Limit nesting and reuse simple blocks.
5. Unsuitable hosting
Overloaded hosting slows everything down, whatever optimisation you do. Check the PHP version (recent versions are much faster), whether OPcache is enabled, and where the servers are compared with your visitors.
6. Too many external scripts
Ad pixels, chat widgets, fonts, maps, embedded videos: every external service adds loading time. In practice, load videos only on click, group your pixels and prefer system fonts where possible.
7. A cluttered database
Post revisions, spam comments and data left behind by old plugins: the database grows over time. Regular clean-ups, after a backup, make queries lighter.
8. Caching used as a sticking plaster
Caching is useful, but it does not fix a heavy theme or 4 MB images. Worse, when badly configured it sometimes shows old content or breaks a cart. As a result, you should build light first and only then add caching if needed.
Optimise or rebuild: how to decide?
Sometimes, fixing things one by one costs more than starting from a clean base. For example, if the theme has been abandoned by its developer, it is better to replace it. Likewise, if the site piles up more than thirty plugins, a light rebuild is often more cost-effective.
On the other hand, if the structure is clean, a few targeted fixes are enough: images, external scripts and hosting. So always start with a measured diagnosis. Then decide. Finally, keep a backup before every change, because a failed optimisation can break a contact form or a cart.
How to measure your site speed
- Test your main pages with PageSpeed Insights, on mobile.
- Monitor the Core Web Vitals, explained in detail on web.dev.
- Test from a real phone on 4G, not only from your office desk.
- Run the test again after every significant change and compare with the previous result.
Our approach: speed built in
A slow WordPress site is not inevitable. Our sites are built with a light theme, automatically converted images and the bare minimum of plugins. See our WordPress service and our mobile-first approach, or ask for an audit of your site.