This plugin lets you manage and automatically purge your hosting's LWSCache whenever you edit your website's content

Aurélien LWS

LWS Cleaner

LWS Hide Login

Secure your access to the admin page with this plugin !

LWS Optimize – All-in-One Speed Booster & Cache Tools

All-in-one speed optimization: caching, WebP/AVIF, Critical CSS, lazy loading, CDN, and more. Instantly boost Core Web Vitals and site speed!

LWS Tools

Optimize and modify your website's parameters

LWS SMS

LWS Affiliation

Add banners and widgets from the affiliate program of LWS.

This plugin, created by <a href="https://www.lws.fr" rel="nofollow ugc">LWS</a> help to automatically manage your LWSCache purge when you edit your pages, post, messages…
It provide a way to purge all your LWSCache.
This plugin works only on servers using the LWSCache system. This cache is pre-installed with Classic shared <a href="https://www.lws.fr/hebergement_web.php" rel="nofollow ugc">web hosting</a>, <a href="https://www.lws.fr/hebergement_wordpress.php" rel="nofollow ugc">WordPress hosting</a> and soon <a href="https://www.lws.fr/hebergement-cpanel.php" rel="nofollow ugc">cPanel hosting</a> from LWS.
The loading speed of your site is crucial to its success. The more visitors your site has, the more RAM and CPU memory the system uses. The page is loaded slowly. So you need a cache system to avoid reloading the page when it is not necessary.
In addition, the site’s page load speed is used in Google’s ranking algorithm. So caching plugins that can improve load times will improve your SEO ranking. Low rankings, and therefore insufficient exposure, often do not allow you to make a living from your website. The loading time of most websites is less than three seconds. Beyond that, many users have already left the page.
The LWS Cache tool is a system designed and developed by LWS. It optimize the loading performance of your website through the use of advanced caching mechanisms, configured at the server level. The tool uses the technologies provided by NGINX.
<h4>Functioning</h4>
When LWS Cache is enabled, a cache server is introduced between the visitor and the web server. 
The aim is to reduce the number of script executions required. For that it keeps the result of the execution in memory for future requests requiring the same response. This means that the same script is no longer executed several times to achieve the same result.
Thus, we eliminate the waiting time of the script execution on the page loading time. At the same time, we save the resources used during the script execution.
<ul>
<li>The visitor requests the page from the web server. Example: index.php. LWS Cache checks if the page has already been generated and stored in the cache</li>
</ul>
If yes, the page is returned directly to the visitor without the need to access the web service and without executing the script
If not, the page is requested to be generated on the web service as a result of the script execution (PHP, NodeJS, Perl, Ruby, …).
<ul>
<li>Once the page is generated, LWS Cache determines if the page can be cached (via headers, URL, …)</li>
</ul>
If yes, the page is saved in the cache and returned to the visitor
If not, the page is saved in the microcache (short-lived cache) and returned to the visitor
<h4>Managing LWS Cache with the plugin</h4>
The WordPress LWS Cache plugin allows you to automatically purge the cache of your pages when you modify them or when you add/approve comments.
To manage the plugin, once connected to your WordPress administration console, go to the “Settings” menu and then “LWS Cache”.
From the settings page, you can enable/disable automatic emptying. You can define when to automatically empty the LWS Cache and completely purge the cache.
A button for emptying the entire cache can be found anywhere in the WordPress admin console (in the quick access bar at the top of the screen).
<h4>Key Features</h4>
Several settings are available to manage your LWS Cache, you can enable or disable these settings:
<ul>
<li>
Automatic purge
</li>
<li>
Home Page Purge (when a post is modified or added, when a published post is trashed)
</li>
<li>
Purge Post/Page/Custom Post Type (when a post is published, when a comment is approved/published, when a comment is unapproved/deleted)
</li>
<li>
Purge Archives (date, category, tag, author, custom taxonomies)
</li>
<li>
Purge all cache
</li>
</ul>

Alternatives to LWSCache

Top alternatives