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.

Web Guy

<p><a href="https://github.com/webguyio/snappy/issues" rel="nofollow ugc">💬 Ask Question</a> | <a href="mailto:webguywork@gmail.com" rel="nofollow ugc">📧 Email Me</a></p>
<p>Caching for a snappier website.</p>
<p>When a WordPress page loads normally, it goes through:</p>
<ol>
<li>PHP execution</li>
<li>Database queries (often 20-50+ queries)</li>
<li>Theme processing</li>
<li>Plugin execution</li>
<li>HTML generation</li>
</ol>
<p>With Snappy file-based caching, it skips all that and just serves a static HTML file.</p>
<p>Estimates for performance improvement:</p>
<ul>
<li>2x faster is conservative and achievable for most sites</li>
<li>5x faster is realistic for database-heavy sites</li>
<li>10x faster is possible for poorly optimized sites with many plugins</li>
</ul>
<h4>Advanced Version</h4>
<p>Snappy is fully capable with its core caching capability, but if you want or need additional optimization and control, advanced settings are available at <a href="https://snappywp.me/" rel="nofollow ugc">snappywp.me</a>.</p>
<ul>
<li>HTML, CSS, and JavaScript minification</li>
<li>GZIP compression</li>
<li>Lazy loading for images and videos</li>
<li>Video embed optimization (YouTube/Vimeo facades)</li>
<li>Font preloading</li>
<li>Database cleanup (spam, revisions, transients)</li>
<li>Automatic weekly database optimization</li>
<li>Cache preloading from sitemap</li>
<li>Defer JavaScript with exclusions</li>
<li>Critical CSS extraction and inlining</li>
<li>WordPress Heartbeat control</li>
<li>Resource hints (preload, prefetch, DNS-prefetch)</li>
<li>Browser caching headers via .htaccess</li>
<li>Security headers (X-Frame-Options, CSP, etc.)</li>
<li>Cloudflare integration with optimized settings</li>
<li>CDN integration with URL rewriting</li>
<li>Settings import/export</li>
<li>Self-hosted update system</li>
</ul>


WeAmp Cache Control for ModPageSpeed vs Snappy