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.

Jose Mortellaro

<p>Update Page Cache flushes and generates again the page cache.</p>
<p>The actual version supports <a href="https://wordpress.org/plugins/w3-total-cache/" rel="ugc">W3 Total Cache</a>, <a href="https://wordpress.org/plugins/wp-fastest-cache/" rel="noopener ugc">WP Fastest Cache</a>, <a href="https://wordpress.org/plugins/wp-super-cache/" rel="ugc">WP Super Cache</a>, and <a href="https://wordpress.org/plugins/wp-optimize/" rel="ugc">WP Optimize</a>.</p>
<p>When you modify a page and save it, usually caching plugins automatically clear the cache of that page, but you need to visit again the page to generate again the cache.</p>
<p>Update Page Cache adds a button on every single page, post and custom post type that you can click to automatically clear and regenerate the cache of that page. Be careful, you will not see the button if you have Fullscreen mode active.</p>
<p>When you edit a single page, if you click on the “Update Page Cache” button, the cache of that page will be automatically updated without the need to visit that page.</p>
<p>In the main settings you can set for each post types if the plugin should automatically clear the page cache when that single post type is saved.</p>
<p>You can also decide which page caches should be updated after saving a specific post type.<br />
In the example shown in the screenshot of the main settings, when a single blog post is saved Update Page Cache updates the cache of the blog page and homepage. When a contact form is saved, Update Page Cache updates the cache of the page Contact.</p>
<h3>Backend Speed Optimization</h3>
<p>Is your dashboard slow? We optimize admin performance by improving queries and reducing plugin load.<br />
Read <a href="https://josemortellaro.com/backend-speed-optimization/" rel="nofollow ugc">Backend Speed Optimization Service</a> for more information.</p>


Update Page Cache

I'm the author of this plugin, but I'm also a user. I'm installing it on the websites where I use caching plugins and I love it. I love my own plugin, I think it does what is written in the description and make save time. So even though I'm the author, I give it 5 stars.

Author and user

Update Page Cache flushes and generates again the page cache. Compatible with W3 Total Cache, WP Fastest Cache, WP Super Cache, WP Optimize.

WeAmp Cache Control for ModPageSpeed vs Update Page Cache