LWSCache vs Cache External Scripts

Often when trying to optimize the Google Pagespeed score, there is one script which still causing the ‘Leverage browser caching’ rule popping up: Google’s own gtag.js and/or analytics.js file… With this plugin you will be able to cache this file on your local server and enable browser caching for longer than 2 hours. The plugin will check every day if there is a newer version of the file to keep the cache up to date.

This plugin, created by LWS 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 web hosting, WordPress hosting and soon cPanel hosting 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. Functioning 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. 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 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, …). Once the page is generated, LWS Cache determines if the page can be cached (via headers, URL, …) 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 Managing LWS Cache with the plugin 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). Key Features Several settings are available to manage your LWS Cache, you can enable or disable these settings: Automatic purge Home Page Purge (when a post is modified or added, when a published post is trashed) Purge Post/Page/Custom Post Type (when a post is published, when a comment is approved/published, when a comment is unapproved/deleted) Purge Archives (date, category, tag, author, custom taxonomies) Purge all cache