Performance Optimisation installs like any other plugin, but activation writes a few files outside its own folder. This page lists the requirements, walks through both install methods, and gives you a checklist for the first minutes after activation.
Requirements
| Requirement | Details |
|---|---|
| WordPress | 6.2 or newer, tested up to 7.1 |
| PHP | 8.2 or newer |
| Redis | Optional, needed only for the object-cache drop-in |
Install the plugin
The release ZIP ships from the GitHub releases page. To install through the admin:
- Download the latest release ZIP.
- In your dashboard open Plugins, then Add New, and click Upload Plugin.
- Select the ZIP file and click Install Now.
- Click Activate.
With WP-CLI, once the ZIP is on the server:
wp plugin install performance-optimisation.zip --activateWhat activation writes
Activation writes two drop-in files into wp-content: advanced-cache.php for page caching and object-cache.php, which is optional and tied to the object cache. It also generates server rules for .htaccess or nginx. Drop-ins load early in every request, which is why they live outside the plugin folder.
Existing drop-ins
If another plugin has already placed its own object-cache.php or advanced-cache.php in wp-content, the two will conflict. Remove the other plugin’s drop-in before activating this one.
First-run checklist
- Check the object cache state with
wp wppo object_cache status. - If Redis is configured, confirm connectivity with
wp wppo object_cache ping. - Turn on minification and script delay in the settings screen.
- Warm the page cache with
wp wppo cache preload.
Verify it works
- View source on a front-end page: cached HTML is shorter and carries the plugin’s cache markers.
- Response headers show a cache hit plus
Server-Timingentries. - Compare a PageSpeed Insights run against your pre-install numbers.
- The built-in Pagespeed screen in the admin reports the same data without leaving WordPress.
Test on staging first
Try each feature on a staging copy before production. Enable one thing, measure, then move to the next: a regression is far easier to trace when only one setting changed.
Hard refresh
Your own browser may keep serving old CSS and JavaScript from its local cache after you enable caching. Do a hard refresh (Ctrl+Shift+R, or Cmd+Shift+R on macOS) before deciding something is broken.