A slow WordPress site can make browsing frustrating, complicate a purchase or discourage someone from requesting a quote. Start by finding what actually delays your visitors. Caching can help, but images, your theme, plugins and external services also deserve attention.
1. Describe the slowdown before changing the site
Record two or three affected URLs and the times you observed the problem. Compare a public page, a form or product page, and the WordPress dashboard. Explain whether the issue is new, constant or intermittent, and whether it began after an update.
- Test on a phone and a computer, noting the browser and connection type.
- Compare a logged-out visit with your administrator session. Personalized pages can follow a different path through the cache.
- Repeat measurements under similar conditions. One result is not enough to establish a pattern.
Performance tools distinguish simulated tests from visitors' real experience. See Google's explanation of performance measurement. A score is an indicator: also check that people can read, navigate and complete their tasks comfortably.
2. Make the change reversible
Before changing caching or plugins, prepare a recoverable backup of both files and the database. Record the existing settings. Use a WordPress staging environment for significant changes. Do not copy its database over the live site without accounting for orders, form submissions and other data received since the staging copy was created.
Change one thing at a time, then check the result. If the slowdown includes errors or a blank page after a change, start with our WordPress troubleshooting guide instead.
3. Use LiteSpeed Cache with appropriate settings
LiteSpeed Cache for WordPress, developed by LiteSpeed Technologies, manages caching and several optimization features. On compatible Nuagerie hosting, it is an option for serving public pages more efficiently. Page caching requires a compatible LiteSpeed environment or QUIC.cloud: activating the plugin alone does not confirm that this cache is working.
- Check whether LiteSpeed Cache is already installed and configured. Preserve its settings before making changes.
- Identify the plugin currently handling full-page caching. Avoid running two at once; plan the switch and clearing the previous cache if needed.
- Once compatibility is confirmed, start with page caching under LiteSpeed Cache > Cache > Cache, with Enable Cache turned on. Follow the LiteSpeed beginner's guide instead of applying an aggressive profile found online.
- Keep advanced optimizations optional. Redis, CDN or QUIC.cloud features may require separate configuration or services.
For an eligible public page, your browser's network tools may show X-LiteSpeed-Cache: hit after an initial load. This confirms that the response came from LiteSpeed's cache. A CDN can affect what you observe: follow the official verification procedure or ask us to check that page's delivery path.
4. Protect personalized journeys
Browser caching, server page caching and CDN caching are different layers. A change may remain hidden if another layer retains an older version. Identify the relevant layer before clearing it; repeatedly purging every cache does not correct a configuration problem.
Do not force carts, checkout, customer accounts or private content into a shared public cache. Check the exclusions provided by your store and test the complete journey. LiteSpeed's cache settings distinguish public, private and excluded content. If Cloudflare is involved, its cache rules must also respect those requirements.
5. Reduce what still slows the page down
- Images: use dimensions suited to their display size and compression that preserves their usefulness. Caching does not make an unnecessarily large image smaller.
- Theme and plugins: review features you actually use, overlapping functionality and recent additions. Test changes before removing a component the site depends on.
- External services: check how embedded videos, tracking tools and widgets affect the pages concerned.
The WordPress performance documentation covers these factors. Options that delay or transform JavaScript and CSS need individual testing: they can break menus or forms. If this happens, undo the relevant setting and consult LiteSpeed's CSS and JavaScript optimization troubleshooting guide.
6. Choose the next step with Nuagerie
After each change, check important pages, forms and, where applicable, the cart and checkout using a controlled test scenario. Keep your before-and-after measurements and a record of the settings you retained.
If the slowdown continues, open a request through your Nuagerie client area with affected URLs, observation times and recent changes, without passwords or customer data. We can help direct the investigation and distinguish hosting checks from work needed within the website.
Would you prefer us to handle improvements? Tell us about your goals. Depending on the findings, targeted optimization, a hosting adjustment or a website redesign may be appropriate. The scope and any costs should be agreed first; a new website should address your needs, rather than a single test score.
