nigro.simone

<p>Speed Up – Page Cache was constructed for made caching dead simple. Simple one-click install. That’s it.</p>
<p>When a page is rendered, php and mysql are used. Therefore, system needs RAM and CPU.<br />
If many visitors come to a site, system uses lots of RAM and CPU so page is rendered so slowly. In this case, you need a cache system not to render page again and again. Cache system generates a static html file and saves. Other users reach to static html page.</p>
<p>After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.</p>
<p>The static html files will be served to the vast majority of your users:<br />
– Users who are not logged in.<br />
– Users who have not left a comment on your blog.<br />
– Or users who have not viewed a password protected post.<br />
99% of your visitors will be served static html files. One cached file can be served thousands of times.</p>
<p>In addition, the site speed is used in Google’s search ranking algorithm so cache plugins that can improve your page load time will also improve your SEO ranking.</p>


Speed Up – Page Cache

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

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.

Speed Up – Page Cache vs WeAmp Cache Control for ModPageSpeed