WP Optimizer – PageSpeed, Cache, Minify, Image Optimization & Core Web Vitals

WP Optimizer brings performance, maintenance, diagnostics and site-management tools into one modular WordPress plugin.

You can use the complete toolkit or enable only the modules your site needs. Its main optimization tasks run on your server, with no required subscription, cloud service or CDN.

Cache and front-end performance

WP Optimizer provides separate cache layers for different types of work:

• Static Page Cache stores complete HTML responses so repeat visits do not rebuild the page through WordPress, PHP and the database.
• Direct Cache Delivery can serve eligible cached pages before WordPress loads by using server rules generated for the current environment.
• Object Cache integrates with the WordPress object-cache system and can use Redis or Memcached when either service is available.
• WP_Query Cache stores selected WordPress query results and clears affected entries when related content changes.
• Database Query Cache caches selected database results, can be limited to specific tables and invalidates entries when the underlying data changes.

Each cache layer has its own lifespan, URL rules, query-string handling, cookie and user-agent exclusions, purge behavior and scope controls. Reports show hits, misses, writes, disk usage and hit ratio.

When a cache module or direct-delivery option is disabled, WP Optimizer removes the files, drop-ins, server rules and scheduled cleanup tasks managed by that feature.

The plugin can also:

• Minify HTML, CSS and JavaScript independently.
• Optionally combine CSS or JavaScript files.
• Configure browser cache policies.
• Generate GZIP compression rules and optional Brotli directives.
• Apply lazy loading and preload resources related to Largest Contentful Paint.
• Run coordinated PageSpeed transformations before final HTML minification.

Enable asset optimizations one at a time. Themes and plugins can depend on the original file order or markup, so clear the cache and test important pages after each change.

Image optimization and WebP

The Media module processes images on your server without requiring an external optimization subscription.

It can:

• Optimize existing images and generated thumbnails.
• Convert supported files to WebP.
• Process new uploads automatically.
• Scan the WordPress media library or a selected filesystem path.
• Split large jobs into background operations for hosts with limited PHP execution time.
• Help identify and clean unused media.

Because the main media workflow is local, images do not need to be sent to a third-party optimization platform.

Page Test and performance diagnostics

Page Test measures a selected URL through four browser-based steps:

1. A baseline request with WP Optimizer and direct cache delivery bypassed.
2. A clean request using the current configuration.
3. A diagnostic warmup that collects data and populates available caches.
4. A measured request using the warmed configuration.

The comparison reports response time, Time to First Byte, peak memory and response size. Warmup data can reveal slow or repeated database queries, expensive hooks, callback samples, query totals and memory use.

Performance Monitor records request history and helps trace slow execution to WordPress core, the active theme, installed plugins, database queries, hooks or callbacks.

Caching, minification, compression, media optimization, lazy loading and LCP preloading can improve the technical foundation behind Core Web Vitals. Results still depend on the hosting environment, theme, content and third-party scripts, so WP Optimizer does not promise a fixed score. Use the diagnostic tools to measure each change and keep the settings that help your site.

Database, cron and site maintenance

The Database module provides:

• Database cleanup and table optimization.
• Database backups.
• Orphaned-data removal.
• Guarded maintenance actions.
• wp_options inspection and autoload-size analysis.

Create a database backup before running aggressive cleanup operations.

Cron Handler lists scheduled WordPress events and custom schedules. It lets administrators inspect recurring work, manage cron entries and identify obsolete tasks.

WP Info collects details about WordPress, PHP, the database, web server, filesystem and storage use. This provides a single place to review the environment before changing performance settings.

Activity, security and WordPress controls

Activity Log records relevant user, post and term actions. Request monitoring detects common suspicious patterns, including XSS and SQL-injection probes, and supports custom monitoring rules.

WP Security provides configurable WordPress and server hardening. Depending on the selected settings, it can protect sensitive files, restrict unwanted access, add security headers and reduce exposed server information. These controls complement secure hosting, updated software and reliable backups; they do not replace them.

Additional modules can:

• Control updates for WordPress core, plugins and themes.
• Restrict dashboard access or hide the Admin Bar.
• Disable comments, selected Block Editor features and unused WordPress output.
• Remove selected dashboard panels and simplify the administration interface.
• Configure SMTP and log outgoing WordPress email.
• Purge the Cloudflare edge cache when the local cache is cleared.

Configuration backups and recovery

WP Optimizer creates a configuration backup before its main settings are updated. To avoid duplicate snapshots during rapid autosaves, it reuses a backup created within the previous 15 minutes and retains the newest 50 backups.

From the Settings module, administrators can review or delete backups, restore a previous configuration, import or export settings and reset individual modules. Restoring settings runs the normal configuration lifecycle so modules, managed cache drop-ins and generated server rules stay synchronized.

If a fatal error comes from WP Optimizer or a plugin-managed object-cache.php or db.php drop-in, the recovery service can try saved configurations or perform a controlled factory reset. A reset can remove plugin-managed drop-ins, generated server rules, static cache data, minified resources, direct-cache files and scheduled optimization tasks. Recovery does not reset unrelated themes, plugins or server configuration.

Server, WooCommerce and page-builder compatibility

WP Optimizer supports WordPress Multisite and detects Apache, Nginx, LiteSpeed Enterprise and OpenLiteSpeed.

• Apache and LiteSpeed Enterprise use managed rules in the local .htaccess file.
• Nginx uses a generated configuration file that must be included in the website server block before Nginx is reloaded.
• OpenLiteSpeed receives compatible rewrite rules for direct cache delivery, redirects and rewrite-based security controls. Enable Auto Load from .htaccess for the virtual host. Configure compression, response headers, MIME types and other non-rewrite options in WebAdmin, then restart OpenLiteSpeed after rewrite changes.

WooCommerce cart, checkout and account routes are excluded from caching and runtime HTML optimization. Session cookies, add-to-cart requests, WC API calls, WooCommerce AJAX and session-storage queries also bypass incompatible cache layers. Custom WooCommerce page slugs are detected from their configured page IDs.

Elementor, Beaver Builder, Divi, Gutenberg, Bricks, Oxygen and Breakdance editor and preview requests bypass cache and output transformations. Builder assets are not rewritten by the CSS or JavaScript minifier, and generated markup is preserved during HTML minification.

WP Optimizer can coexist with other performance plugins, but only one plugin should manage each cache, minification, asset-combination or server-rule layer.

Recommended setup

For an existing or production site:

1. Review the environment in WP Info.
2. Enable browser caching, supported compression and image optimization for new uploads.
3. Create a database backup before cleanup.
4. Enable the standard page cache and test dynamic pages.
5. Configure direct cache delivery only after the standard cache works correctly.
6. Enable extra cache layers only when the required server services are available.
7. Activate HTML, CSS and JavaScript optimization separately.
8. Clear generated caches after important setting changes.
9. Test forms, search, login, account and checkout flows.
10. Use Page Test and Performance Monitor to verify the result.