- Listing audit
- 48/100
WeAmp Cache Control for ModPageSpeed is a WordPress Plugin Directory app by oschaaf.
AppRanks verdict
Generated from marketplace data as of Sep 11, 2026
WeAmp Cache Control for ModPageSpeed is a WordPress app. It has no reviews on WordPress yet.
Pros
- No standout positives in the measured data.
Cons
- −No reviews yet — fit and reliability are unverified by other merchants
How WeAmp Cache Control for ModPageSpeed works
Show full descriptionShow less
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.
The plugin does three things:
Enables full-page caching — adds Cache-Control: public, max-age=N 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.
Keeps the cache fresh — 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.
Gives you control in WP Admin and WP-CLI — per-post-type TTLs, cookie bypass list, excluded URL patterns, a first-run setup wizard, and wp pagespeed flush|status|test-connection commands.
Works with both ModPageSpeed product lines (auto-detected), with one important difference:
ModPageSpeed 2.0 caches full HTML pages itself — the plugin’s headers and purge calls drive the module’s page cache directly.
mod_pagespeed / ngx_pagespeed 1.1 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 proxy_cache, Varnish, or a CDN) plus ModifyCachingHeaders off or DownstreamCachePurgeLocationPrefix — with 1.1’s default ModifyCachingHeaders on, 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.
Server requirements
ModPageSpeed 1.1 (v1.15.0+r3 or later) or ModPageSpeed 2.0 (v2.0.0 or later) installed on your web server.