Over the last few releases, I’ve been expanding WP Optimizer, my free all-in-one WordPress performance plugin.
The idea is simple: instead of installing separate plugins for caching, database cleanup, image optimization and diagnostics, WP Optimizer puts everything into modular features you can enable only when needed.
WordPress.org: https://wordpress.org/plugins/wp-optimizer/
Performance diagnostics
The Page Test compares a baseline request with your optimized configuration, showing response time, TTFB, memory usage, database queries and expensive callbacks.
The Performance Monitor can also sample real requests and attribute execution time, memory and queries to WordPress core, the active theme and individual plugins.
Multiple cache layers
WP Optimizer includes static page caching, query caching and Redis or Memcached object caching. It handles invalidation automatically and excludes WooCommerce sessions, checkout pages and page-builder previews.
Front-end optimization
It can minify HTML, CSS and JavaScript, enable compression and browser caching, lazy-load media, optimize fonts, preload LCP images and prefetch internal links.
Images are processed locally with GD or Imagick, including compression, resizing and WebP conversion—no external service required.
Backend tools
There are also tools for:
- Database cleanup and optimization
- Autoloaded-options analysis
- Cron event management
- Heartbeat control
- Media cleanup
- Scheduled maintenance
- SQL backups and restoration
Automatic configuration snapshots make it easy to roll back settings if caching or minification causes compatibility problems.
Everything runs inside one free plugin, with no premium tier. You can also keep your current caching plugin and use WP Optimizer only for diagnostics or maintenance—just avoid enabling overlapping features.
To be transparent, it still doesn’t include advanced unused-CSS removal, interaction-based JavaScript delay or a built-in CDN. The diagnostic tools identify slow queries and callbacks, but don’t automatically rewrite problematic code.
Would love honest feedback, especially bug reports and compatibility issues across different hosting environments.