Optimize WordPress
Speed up WordPress while protecting logged-in pages, shopping carts and checkout. More optimization plugins do not automatically mean better performance.
Measure before changing settings
Back up the site, choose a repeatable page or API request, and record load time, server response time, errors, memory and CPU use. Test while signed out and signed in. Change one thing at a time on staging before applying it to production.
Steps
- Update supported WordPress, plugins, themes and PHP on staging after making a restorable backup.
- Use one coordinated page-cache layer. Exclude administration, logged-in sessions, cart, checkout and personalized pages. Verify the exclusions as a customer.
- Resize and compress images; use modern image formats where supported. Do not lazy-load the main above-the-fold image if it delays the first view.
- Remove unused plugins and themes after checking dependencies. Measure expensive plugins rather than disabling security blindly.
- Use persistent object caching only when a compatible cache service is available. A configuration flag alone does not create a working cache backend.
- Review database size, slow queries and scheduled tasks. Replace request-triggered scheduling only after a reliable server scheduler is configured and verified.
Check the result
Repeat the same measurements and confirm login, forms, uploads and checkout still work. Keep the change only if it improves the measured problem without causing errors. Clear only the relevant cache and keep a rollback copy.
Related articles
Last reviewed
2026-10-28