andresmesi

Mesi Cache converts your WordPress site into a fully static HTML version served 
directly by Apache. Once a page is cached, it is delivered instantly without 
executing PHP or querying MySQL.
This design removes the need for PHP-FPM and database access on every visit, 
reducing server load to almost zero. The result is a pure static experience with 
instant page delivery and total control over your server resources.
Mesi Cache is minimalist, open, and transparent. It integrates cleanly with 
 .htaccess, uses no cron jobs, and requires no external services.
What it does 
* Creates static HTML files of posts, pages, categories and authors. 
* Serves files directly from disk, bypassing PHP and MySQL completely. 
* Invalidates relevant cache files when new content is published. 
* Allows manual cache generation and cleaning from the admin panel. 
* Works in root and subdirectory installations. 
* 100% local — no APIs, no remote calls, no external dependencies.
What it does not do 
* No CSS or JS minification. 
* No CDN integration (can be added manually). 
* No object or fragment caching. 
* No user/session-aware pages or dynamic content. 
* Does not serve cached content to logged-in users.
Mesi Cache focuses purely on static HTML delivery for public visitors. 
When cached, pages are served as plain files — no PHP or database code executes.
The plugin code is open, commented, and easy to extend. 
Developers can add features like preloading or CDN hooks using ChatGPT, Gemini, 
or manual edits.
<h3>License</h3>
This plugin is licensed under GPLv2 or later. 
You are free to use, modify, and redistribute it.

Mesi Cache

Ultra-light static HTML caching system for WordPress.

PiotrPress

Clearcode

The CC-Cache plugin supports caching of Posts, Pages, and any public Custom Post Types – including single and archive pages. 
It also supports a “static page display” option: Front page, Posts page, and standard Latest Posts listing. 
This plugin is compatible with Multisite WordPress installations.
<h4>How does it work?</h4>
When a user (i.e. someone who is logged out of WordPress) opens a page for the first time, the plugin saves all the rendered html to a file in the wp-content/cache directory. 
From this moment onwards, any user who accesses the site will be served content directly from the generated html file. WordPress at this point is not initialized for this page. 
The generated cache file will be removed when you make changes to the corresponding Post/Page, and then the process starts from the beginning. 
You can also clear all cached files from the Cache options page (visit the ‘Settings > Cache’ page in wp-admin), or manually delete files from the wp-content/cache directory.
<h4>Tips & Tricks</h4>
You can check if a page’s content is served from a cache file by opening the page’s source code in the browser and scrolling down to the closing <code><body></code> html tag. 
If the content is cached, you should see a comment with the date and time the page was last cached, for example: 
 
You can disable cache for a single request and get the raw html by adding <code>cache=false</code> to a URL’s parameter, for example: 
 http://example.com/?cache=false
You can disable cache for a single request and get the raw html by adding <code>cache=false</code> HTTP header.
Logged-in users always get the raw html.
<h4>Ideas for future versions</h4>
<ol>
<li>Add support for Categories, Tags, Taxonomies, and Authors.</li>
<li>Add support for RSS/Atom feeds.</li>
<li>Add support for Nginx and IIS servers.</li>
<li>Add support for other WordPress Filesystem Methods.</li>
<li>Add regenerate function for all cache files.</li>
</ol>
<h3>Requirements</h3>
<ol>
<li>Apache server</li>
<li>mod_rewrite</li>
<li>Write access to wp-content/cache directory</li>
<li>PHP interpreter version >= 5.3</li>
</ol>

CC-Cache

A simple and fast cache plugin based on static-rendered html files served by Apache with mod_rewrite.

Mesi Cache vs CC-Cache