oschaaf

<p>This plugin is the control panel for ModPageSpeed — a web server optimization module for nginx and Apache. ModPageSpeed must be installed and running on your server for this plugin to function. It is not a standalone caching plugin.</p>
<p>The plugin does three things:</p>
<ol>
<li><strong>Enables full-page caching</strong> — adds <code>Cache-Control: public, max-age=N</code> to anonymous page responses (WordPress does not send this by default), with explicit bypasses for logged-in users, WooCommerce cart/checkout/account pages, search, feeds, and 404s.</li>
<li><strong>Keeps the cache fresh</strong> — calls the ModPageSpeed purge API when you publish, update, or delete content, when comments change, when stock levels change, and when terms or theme settings change.</li>
<li><strong>Gives you control in WP Admin and WP-CLI</strong> — per-post-type TTLs, cookie bypass list, excluded URL patterns, a first-run setup wizard, and <code>wp pagespeed flush|status|test-connection</code> commands.</li>
</ol>
<p>Works with both ModPageSpeed product lines (auto-detected), with one important difference:</p>
<ul>
<li><strong>ModPageSpeed 2.0</strong> caches full HTML pages itself — the plugin’s headers and purge calls drive the module’s page cache directly.</li>
<li><strong>mod_pagespeed / ngx_pagespeed 1.1</strong> does not cache HTML (it is a streaming rewriter; its in-place optimization caches only images, CSS, and JS). Full-page caching on 1.1 requires an external cache layer in front (nginx <code>proxy_cache</code>, Varnish, or a CDN) plus <code>ModifyCachingHeaders off</code> or <code>DownstreamCachePurgeLocationPrefix</code> — with 1.1’s default <code>ModifyCachingHeaders on</code>, the module replaces this plugin’s Cache-Control header on rewritten HTML. On 1.1, the plugin’s purge calls evict optimized sub-resources and metadata, not HTML pages.</li>
</ul>
<h4>Server requirements</h4>
<ul>
<li>ModPageSpeed 1.1 (v1.15.0+r3 or later) or ModPageSpeed 2.0 (v2.0.0 or later) installed on your web server.</li>
<li>For 2.0: the worker admin API enabled (<code>--api-port</code>).</li>
<li>For full logged-in-user correctness an nginx cookie-bypass map block is required — the setup wizard provides a copy-paste snippet and verifies it.</li>
</ul>
<h4>WP-CLI</h4>
<ul>
<li><code>wp pagespeed flush [--url=<url>]</code> — purge the home page (and posts page), or one specific URL on this site.</li>
<li><code>wp pagespeed status</code> — detected product, version, license tier, purge prerequisites, and last-purge status.</li>
<li><code>wp pagespeed test-connection</code> — verify the admin API is reachable and correctly configured (read-only, never purges).</li>
</ul>
<h4>License</h4>
<p>This plugin is free software, licensed under the GNU General Public License v2.0 or later. The full GPL-2.0 license text is bundled with the plugin in the LICENSE file.</p>
<h3>Third Party Services</h3>
<p>This plugin makes HTTP requests to the operator-configured ModPageSpeed admin API URL. Data sent includes page URLs (for cache purging) and an API key (for authentication). No data is sent to We-Amp or any third party.</p>


WeAmp Cache Control for ModPageSpeed

Full-page caching control panel for the ModPageSpeed server module: cache headers, purge-on-publish, per-post-type TTLs.

Taylor Lovett

<p>Simple Cache was constructed after getting frustrated with the major caching plugins available and building sites with developer-only complex caching solutions that get millions of page views per day. Simple Cache promises the following:</p>
<ul>
<li>Extremely simple one-click install. There is an on-off switch. That’s it. No need to wade through 50 complicated settings.</li>
<li>Simple Cache makes your site run very fast so you can handle lots of traffic.</li>
<li>Extremely easy to delete. Don’t like the plugin? You can remove it, and your website won’t break.</li>
<li>Easily clear the cache if you need to.</li>
<li>Enable gzip compression</li>
<li>Want to get advanced with object caching (Memached or Redis)? An advanced mode is available that will automatically setup <a href="https://wordpress.org/plugins/batcache/" rel="ugc">Batcache</a> and <a href="https://wordpress.org/plugins/memcached/" rel="ugc">Memcached</a>/<a href="https://wordpress.org/plugins/wp-redis/" rel="ugc">Redis</a> for you.</li>
</ul>
<p>If you need your site to run fast, don’t have time to mess with complicated settings, and have been frustrated by other caching plugins, give Simple Cache a try.</p>
<p>Pull requests are welcome on <a href="https://github.com/tlovett1/simple-cache" rel="nofollow ugc">Github</a>.</p>
<h3>Support</h3>
<p>For full documentation, questions, feature requests, and support concerning the Simple Cache plugin, please refer to <a href="http://github.com/tlovett1/simple-cache" rel="nofollow ugc">Github</a>.</p>


Simple Cache

I had this plugin on about 30 sites two years ago, but have since removed it, one by one, because of bad experiences of many kinds. The last was removed today, after site crashed due to fatal error in caused by the last update to this plugin.

When deactivating it also puts DEFINE('WP_ACHE', false); at the top of wp-config.php. This is bad and makes trouble using another cache plugin, unless this line is manually removed.

I can not recommend this plugin. Be aware of the thing mentioned above, when uninstalling to try out another.

Sorry - bad plugin

A very simple plugin to make your site run lightning fast with caching.

WeAmp Cache Control for ModPageSpeed vs Simple Cache