peterarends

Simple Page Cache is an extremely simple, super-fast page cache for WordPress. The plugin stores full HTML pages on disk for non-logged-in visitors. The cache is automatically cleared when content is updated, ensuring visitors always see fresh content. Ideal for small to medium-sized sites and webshops that want maximum speed without complex settings.
Main features: 
– Caching for non-logged-in users (GET requests only) 
– Path-based cache structure for nginx direct serving (<code>/host/path/index.html</code>) 
– Cache files are stored in <code>/wp-content/uploads/simple-page-cache/</code> 
– Drop-in (<code>advanced-cache.php</code>) for maximum speed before WordPress loads 
– Nginx configuration generation for direct cache serving 
– Automatic cache clearing when posts/pages are updated 
– E-commerce integration with intelligent cache clearing for: 
 – WooCommerce (orders, stock updates, product changes) 
 – Easy Digital Downloads (purchases, download updates) 
 – BigCommerce for WordPress (product updates) 
 – Generic e-commerce plugins (product post types) 
– Automatic detection of dynamic pages (cart, checkout, account, wishlist) for: 
 – WooCommerce 
 – BigCommerce for WordPress 
 – Easy Digital Downloads 
 – iThemes Exchange 
 – Jigoshop 
 – WP-Shop 
– Detected dynamic pages are automatically excluded from caching 
– Manual cache clearing via admin bar button 
– Nginx config regeneration via admin bar button 
– Performance comments in cached HTML files 
– No complex settings, no database writes
<h3>Nginx Configuration</h3>
For maximum performance, you can configure nginx to serve cached files directly without PHP processing:
<ol>
<li>Copy the nginx configuration from <code>/wp-content/uploads/simple-page-cache/nginx.conf</code></li>
<li>Add the configuration to your nginx server block for your domain</li>
<li>Test nginx configuration: <code>sudo nginx -t</code></li>
<li>Reload nginx: <code>sudo systemctl reload nginx</code></li>
</ol>
The nginx configuration includes: 
– Internal location block for serving cached files 
– Automatic cache bypass for logged-in users 
– Automatic cache bypass for requests with query strings 
– Debug headers to identify cache hits
Benefits of nginx direct serving: 
– Faster response times (no PHP processing) 
– Lower server load 
– Better scalability 
– Direct file serving from disk
<h3>How it works</h3>
<ul>
<li>For every non-logged-in visitor and every GET request, a static HTML file is created and served.</li>
<li>Path-based cache structure: Cache files are organized as <code>/host/path/index.html</code> for direct nginx serving.</li>
<li>Pages with characteristics of dynamic e-commerce pages (such as cart, checkout, account, wishlist) are automatically detected and excluded from caching. The plugin recognizes WooCommerce, BigCommerce, Easy Digital Downloads, iThemes Exchange, Jigoshop, and WP-Shop.</li>
<li>The list of excluded pages is automatically maintained in a file in the cache directory.</li>
<li>Automatic cache clearing: When posts or pages are updated, the plugin efficiently clears cache using the new path-based structure and scans for related content.</li>
<li>E-commerce integration: For WooCommerce, when orders are placed or product stock is updated, the plugin automatically clears cache for the affected products and related pages (categories, tags, shop pages, homepage).</li>
<li>Performance comments: Each cached HTML file includes a comment with timestamp and host information for debugging and transparency.</li>
<li>Nginx integration: Generated nginx configuration allows direct serving of cached files without PHP processing for maximum performance.</li>
</ul>
<h3>Clearing the cache</h3>
<ul>
<li>Click the “Clear Page Cache” button in the admin bar (visible to administrators only) to remove all cache files.</li>
<li>Click the “Regenerate nginx.conf” button in the admin bar to regenerate the nginx configuration file.</li>
</ul>
<h3>Deactivation</h3>
<ul>
<li>When deactivating the plugin:
<ul>
<li>The drop-in <code>advanced-cache.php</code> is removed.</li>
<li>The <code>define('WP_CACHE', true);</code> line (if placed by this plugin) is removed from <code>wp-config.php</code>.</li>
</ul>
</li>
</ul>

Simple Page Cache

Simple, blazing fast static page cache for WordPress. Caches HTML for non-logged-in users with intelligent cache clearing for e-commerce sites.

Gareth Bult

Welcome to the Make Me Static Plugin for WordPress. This plugin is a static site generator and aims to create and maintain a static copy of your WordPress website within a Git repository. This version includes automatic access to a free Git solution and Page provider platform. (so no setup or credentials are necessary)
Alternatively the static site can be generated and stored in a GitLab Git Repository that can be used as a source for a static page platform such as CloudFlare Pages. The plugin provides customised sitemap and change tracking which connects to an external crawling service which does all the heavy lifting.
We have made great efforts in this version to minimise the configuration required to get going, if you have any problems (with anything) please let is know and we’ll do our best to help. Check out this YouTube video for an introduction to static front-ends and a walk-through of converting a pre-existing WordPress site into a WordPress site with a static front-end.
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/ZJ5IDgZ9u-Q?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<h3>How the service works</h3>
The plugin connects to a directory service on the Internet at one of the directory URL’s listed below. This in turn will point the plugin to a ‘crawler’ that has been allocated to your site. 
When you ask the plugin to make a static copy of your site, it will instruct the crawler to visit all the pages on your site to determine which have changed since it’s last visit. Any changed pages will be copied to a Git repository, which in turn can publish pages directly to a page hosting service.
The default option is to use a Git account hosted by MadPenguin, and to publish the site on MadPenguin’s page hosting platform. As a result the default options do not require any specific Git or Page hosting configuration to get going. If on the other hand you choose to use a hosted Git service such as GitLab, you will need to enter some credentials for your online account, and from there configure your GitLab account to publish to a page hosting service.
Once you have successfully published a static copy of your site, all you need to do is point your domain at the address of the page hosting service, and asssuming your domain matches the one you 
entered when setting up your profile within the plugin, you should be up and running.
The service retains a metadata database for the site which includes file names, sizes and modification times, together with any credentials that have been added when creating a profile. (Sensitive credentials and other information is encrypted at rest). The external service is responsible for all scanning and processing activities to mitigate strain on the WordPress server. 
The only private data transferred to the external service is the information you enter when creating a profile. All other information is obtained via an anonymous external scan, hence publically available. If you have selected the default Git option, then the service will also retain a static copy of the site.
<h3>Useful references</h3>
<ul>
<li><a href="https://makemestatic.com/" rel="nofollow ugc">The service product page</a></li>
<li><a href="https://makemestatic.com/terms-and-conditions/" rel="nofollow ugc">Terms and Conditions of Service</a></li>
<li><a href="https://makemestatic.com/privacy-policy/" rel="nofollow ugc">Privacy Policy</a></li>
<li><a href="https://makemestatic.com/getting-started/" rel="nofollow ugc">Getting Started</a></li>
<li><a href="https://makemestatic.com/service-status/" rel="nofollow ugc">Service Status</a></li>
<li><a href="https://github.com/oddjobz/make_me_static/issues" rel="nofollow ugc">Support Forum</a></li>
</ul>
Make me static directory service URL’s;
<ul>
<li>https://mms-directory-1.madpenguin.uk</li>
<li>https://mms-directory-2.madpenguin.uk</li>
<li>https://mms-directory-3.madpenguin.uk</li>
</ul>
Other URL’s used to load code;
<ul>
<li>https://assets.makemestatic.com, source for stage-2 crawler UI</li>
<li>https://status.makemestatic.com, endpoints that indicate the currently deployed version of a site</li>
<li>https://weblogs.makemestatic.com, source for dynamically loaded weblogs data / websockets</li>
<li>https://mms-crawler-*.madpenguin.uk, location of the actual crawlers (via websocket)</li>
</ul>
Note that this in an integrated solution, the 3rd party crawling service is owned and operated by the plugin authors on a combination of cloud hosted and on premesis equipment.
<h3>Live Web Statistics (experimental)</h3>
If you opt to use the integrated Pages platform, this also provides a live WebStats option that uses the following URL;
<ul>
<li>https://weblogs.makemestatic.com</li>
</ul>
This allows live webstats to be seamlessly delivered into your control panel and updated in real-time via a websocket connection. Do not use this URL directly! 
This URL is only referenced once you click on the webstats icon next to your profile.
<h3>How Does it work?</h3>
The WordPress site is scanned by the MMS service under direction from the WordPress plugin. This off-loads the scanning process to specialised software which aims to minimise the loading on the WordPress server while scans are in progress.
There are three types of scan that can be performed;
<ul>
<li>
An “update”, which literally only looks at entries with changed sitemap timestamps 
(this is very quick and great for typo’s and any changes that only affect a single page)
</li>
<li>
A “synchronise”, typically this will scan every asset on the WordPress site and compare a checksum of each asset against it’s database to see if it’s changed since the last scan. Any changes are then transferred to the connected Git repository.
</li>
<li>
A “Git verification”, this is like a “synchronise”, but also scans the Git repository for assets that are no longer referenced by the site (and removes them).
</li>
</ul>
As the site is scanned “from the outside” there should be no risk of the plugins actions exposing any data that isn’t already public. By the same token the external service has no ability to modify WordPress so the security footprint of the plugin is tiny.
<h3>Feature bullet points</h3>
<ul>
<li>The plugin provides a way to produce a static copy of your website in a git repository</li>
<li>The result is compatible with both Github pages and CloudFlare pages for automatic publication</li>
<li>Multiple profiles are supported for (A+B_…) testing</li>
<li>Various scan rates are supported from one page per 5s to 7 cores flat out</li>
<li>Scheduled updates are supported and automated scanning</li>
<li>Currently “Gitlab” is supported with plans for GitHub and on-prem Gitlab</li>
<li>Support push services (WebPushr) to automatically notify subscribers on scan completion</li>
<li>Issue tracker for each profile to diagnose problems
<ul>
<li>Handles current and historical issues</li>
<li>Ability to acknowlede or delete issues when resolved</li>
</ul>
</li>
<li>GUI access to the internal asset database
<ul>
<li>Search as you type filtering</li>
<li>Pinning (force assets to be scanned regardless of perceived change)</li>
<li>Selective / manual queueing of assets for testing</li>
</ul>
</li>
<li>Ability to include manual / static assets in the scan (in the WP tree but unmanaged by WP)</li>
<li>Ability to exclude specific files and folders</li>
<li>Setup Wizard is included for a guided profile creation</li>
</ul>
<h3>The Technology</h3>

<ul>
<li>The Plugin presents as a WordPress Admin / plugin page</li>
<li>Backend connections are made over websockets using PKI</li>
<li>The crawler respects Robots.txt, (make sure the “MMSbot” agent is allowed on your site)</li>
<li>MMS Javascript runs in an isolated module and CSS “plays nice” with WordPress</li>
<li>Global CSS and theming is partitioned and user editable (if you feel the need …)</li>
<li>All of the front-end JS code and PHP is either GPL2 or MIT licensed</li>
<li>Backend-code is all based on the Orbit Framework (the framework and DB are all MIT licensed)</li>
<li>Orbit is a ‘real time’ framework, so the admin panel is 100% reactive.
<ul>
<li>Progress bar updates are typically “per percent” granularity</li>
<li>All statuses, totals, etc, are updated as they happen</li>
<li>Unless you’ve hit a bug, there is no mileage in reloading the MMS plugin page</li>
<li>If you change your license information, it will change in real-time</li>
<li>If the crawler allocated to your site changes (perhaps due to a license upgrade) then the 
appropriate version of the crawler UI will be uploaded “into” the page from the new 
crawler.</li>
</ul>
</li>
</ul>

Make Me Static, Static Site Generator, Git, Pages and Live Stats

Static site generator using Git for storage. Comes with free integrated Git + Pages solution including Live WebStats.

Simple Page Cache vs Make Me Static, Static Site Generator, Git, Pages and Live Stats