When a WordPress site slows down, the first reaction is often to install yet another cache or optimisation plugin. In reality, adding more code without understanding the problem can make things worse.
To speed up WordPress sustainably, it is better to start from what the site is loading, from the server and from the features you really need.
1. Measure before you act
Use PageSpeed Insights, WebPageTest or Chrome DevTools to understand whether the problem lies in the server, images, JavaScript, layout or interactions.
If you are not sure how to read the results, I explained the difference between real-user data and lab tests in the guide on how to tell whether a WordPress site is really slow.
2. Start from the hosting and TTFB
If the server takes too long to start responding, no front-end work can fully make up for it.
- use a supported, up-to-date PHP version;
- check CPU, RAM and PHP process limits;
- check server-side caching and object cache where useful;
- analyse slow queries and database load.
3. Remove plugins and add-ons you do not need
The number of plugins alone does not determine speed: a well-written plugin can weigh less than a single very intrusive one. The point is to understand what each component loads and where.
- remove unused or duplicate plugins;
- avoid add-ons that load dozens of widgets you never use;
- check scripts and CSS loaded globally;
- replace problematic components only once you have identified their real cost.
4. Optimise images
Resize images according to how they are actually used, and use efficient formats such as WebP or AVIF where appropriate. Compression can be done before uploading or through reliable tools on the site/CDN side: there is no single solution that suits everyone.
Above all, avoid serving images that are much larger than the space they are displayed in.
5. Configure caching without duplicating it
If your hosting already provides page cache, object cache or a CDN, adding another layer may be pointless or create conflicts. Check what is already active first.
There are two in-depth articles on this topic: cache plugins and managed hosting and conflicts between cache and CDN.
6. Load assets only where they are needed
Forms, sliders, popups, maps, chats and widgets do not necessarily need to load their scripts on every page.
When the theme or plugin does not handle conditional loading well, you can step in with configuration, code or dedicated tools. But do it after checking dependencies: disabling a script “at random” can break features that seem unrelated.
7. Check fonts and third-party services
External fonts, analytics, advertising, chats, video embeds and tag managers can affect loading and interactivity. Cut what you do not need and load the rest as efficiently as possible.
8. Do not chase 100/100
A perfect score is not the goal. What matters is offering real users a fast, stable experience and keeping the project maintainable.
Focus on the problems that really affect LCP, INP, CLS, response time and navigation, instead of applying every recommendation automatically.
Conclusion
Speeding up WordPress means, above all, removing bottlenecks and unnecessary complexity. Hosting, images, plugins, assets and caching should be analysed as parts of the same system.
If you want to know where to work on your site, see the WordPress performance and optimisation service or get in touch.