Before
150% Increase in WordPress page load speeds
WebCharger and Litespeed cache transform WordPress and Woo Commerce page load times.
Turbo charge WordPress for even faster page load times
We already offer the fastest possible hardware and software stack, now all WordPress and Woo Commerce hosting come with WebCharger and Litespeed cache as standard. All you need is a simple WordPress plugin.
WebCharger uses the LiteSpeed Cache WordPress plugin to communicate with LiteSpeed Web Server and LSCache to statically cache your dynamic WordPress pages, greatly reducing page load time and server load.
The current version will only cache and serve pages for non-logged in users. After a user has logged in, their page requests will always hit the backend.
It supports WooCommerce Plugin since version 1.0.3 without any extra configuration and no separate plugin required. The Cart, My Account, and Checkout pages are non-cache-able pages according to WooCommerce and we honor the same for current version.
Speed test before and after cache plugin activation
We deliberately built a bloated WordPress site with too many menus and large images to really push the plugin, the results speak for themselves, over a 100% performance increase.
After
Installation
-
Disable any other page caches as these will interfere with LSCWP.
-
Download the LSCWP plugin from our WordPress Plugin Directory page.
-
Log in to your WordPress Dashboard, navigate to “Plugins”, and click on “Add New” → “Upload Plugin”.
-
Select the LSCWP zip file and click “Install Now”.
-
Enable the plugin by navigating to Plugins » LiteSpeed Cache » Settings and checking the box for Enable LiteSpeed Cache.
Testing
You can check if a page is being served from LSCWP by:
-
Navigating to your site from a non-logged-in browser and using your browser’s developer tool to check the response header for the HTML file. Right click on the page and select some form of “Inspect”, then click on the “Network” tab in the inspector.
-
In a different, logged-in browser, navigate to the cache manager and purge your cache.
-
Reload the page in the non-logged-in browser. If you see “X-LiteSpeed-Cache: miss”, “X-LiteSpeed-Cache-Control:public,max-age=1800”, and “X-LiteSpeed-Tag:F,B.1” (as an example), this will store the page in the cache.
-
If you reload page a second time and see “X-LiteSpeed-Cache: hit” in the response header for the HTML file (usually listed first), then the page is being served by the cache and LSCWP is configured correctly.
Turning On Debug Log
To enable the WordPress debug log, modify “wp-config.php” under WordPress’ root directory as follows:
-
Set “WP_DEBUG” to true.
define('WP_DEBUG',true); -
Add the following:
define('WP_DEBUG_LOG',true);
a “debug.log” file should now be generated under “wp-content” which will log information whenever WordPress hits the backend.
You can monitor this log during debugging using the following command:
tail -f wp-content/debug.log