This tutorial shows you how to speed up WordPress with Cache Enabler + Cloudflare CDN. Cache Enabler is a free, lightweight and powerful WordPress caching plugin, it creates static HTML files and stores them on the server’s disk. With the minimal configuration, you will improve site performance for a faster load time.
The VPS used in this article: DigitalOcean (1GB RAM, 1 vCore)
Get $100 of free DigitalOcean credits if you sign up through this link!
LEMP stack used in this article: WordOps
Note: WordOps has provided the best combination of Nginx FastCGI Cache + Redis Object Cache, this article is only used to test the performance of Cache Enabler.
Operating System: Ubuntu 20.04
Please add your domain name to Cloudflare in advance.
Please resolve your domain name to an IP address in advance.
Demo domain: 8.blogwp.ovh
Please replace 8.blogwp.ovh with your own domain name.
You can read this article for a detailed installation of WordOps
1、Install WordOps
wget -qO wo wops.cc && sudo bash wo[email protected]:~# wget -qO wo wops.cc && sudo bash wo
Welcome to WordOps install/update script v3.13.2
Installing wo dependencies [OK]
Installing WordOps [OK]
Running post-install steps [OK]
WordOps (wo) require an username & and an email address to configure Git (used to save server configurations)
Your informations will ONLY be stored locally
Enter your name: blogwpwpblog
Enter your email: [email protected]
Synchronizing wo database, please wait...
WordOps (wo) installed successfully
To enable bash-completion, just use the command:
bash -l
To install WordOps recommended stacks, you can use the command:
wo stack install
To create a first WordPress site, you can use the command:
wo site create site.tld --wp
WordOps Documentation : https://docs.wordops.net
WordOps Community Forum : https://community.wordops.net
WordOps Community Chat : https://chat.wordops.net
Give WordOps a GitHub star : https://github.com/WordOps/WordOps/Note:
Please replace blogwpwpblog with your own name
Please replace [email protected] with your own email
2、Install WordPress + Cache Enabler
wo site create 8.blogwp.ovh --wpce[email protected]:~# wo site create 8.blogwp.ovh --wpce
Start : wo-kernel [OK]
Adding repository for MySQL, please wait...
Adding repository for NGINX, please wait...
Adding repository for PHP, please wait...
Updating apt-cache [OK]
Installing APT packages [OK]
Applying Nginx configuration templates
Testing Nginx configuration [OK]
Restarting Nginx [OK]
Testing Nginx configuration [OK]
Restarting Nginx [OK]
Configuring php7.3-fpm
Restarting php7.3-fpm [OK]
Tuning MySQL configuration [OK]
Restarting mysql [OK]
Running pre-update checks [OK]
Setting up NGINX configuration [Done]
Setting up webroot [Done]
Downloading WordPress [Done]
Setting up database [Done]
Configuring WordPress [OK]
Installing WordPress [OK]
Installing plugin nginx-helper [OK]
Installing plugin cache-enabler [OK]
Setting plugin cache-enabler [OK]
Testing Nginx configuration [OK]
Reloading Nginx [OK]
HTTP Auth User Name: WordOps
HTTP Auth Password : 2Fux8qBsHCiAfmlKG2txINdC
WordOps backend is available on https://64.227.1.210:22222 or https://ubuntu-s-1vcpu-1gb-nyc1-01:22222
WordPress admin user : blogwpwpblog
WordPress admin password : 3ytXPCMp7ADQ59emBwjaxNvS
Cache-Enabler configuration : http://8.blogwp.ovh/wp-admin/options-general.php?page=cache-enabler
Successfully created site http://8.blogwp.ovh3、Install Cache Enabler plugin
Cache Enabler plugin settings
Check “Cached pages expire 0 hours after being created”
Check “Clear the site cache if any post type has been published, updated, or trashed”
Check “Clear the site cache if a comment has been posted, updated, spammed, or trashed”
Check “Clear the site cache if a plugin has been activated, updated, or deactivated”
Check “Pre-compress cached pages with Gzip”
Uncheck Minify HTML in cached pages excluding inline CSS and JavaScript
Click “Save Changes” button.
By pressing the “Clear Site Cache” button, you can easily manually clear the WordPress cache
4、Cloudflare CDN Settings
Click the ‘Speed’ section, click the Optimization tab, turn Auto Minify on, toggle the Brotli switch to On.
Click the ‘Caching’ section, click the Configuration tab. Under Browser Cache TTL section, set the option to Respect Existing Headers.
Click the ‘Network’ section, toggle the HTTP/3 (with QUIC) switch to On, toggle the 0-RTT Connection Resumption switch to On, toggle the gRPC switch to On, toggle the WebSockets switch to On.
5、Cache Enabler Load Testing
Load Testing Tool: loader.io
Load Testing Type: Clients per second and Maintain client load
Twenty Twenty-One theme
Use “FakerPress” plugin to generate 300 posts and 1500 comments.
5.1 Download the verification file
5.2 Upload the verification file. When use WordOps, the verification file of loader.io need to be uploaded to /var/www/8.blogwp.ovh/htdocs
5.3 Click “Verify” button, shows “Congrats, target verification passed!”
Load Test after enable Cache Enabler
250 clients per second in 1 minute, the average response time is 14 ms.
500 clients per second in 1 minute, the average response time is 14 ms.
750 clients per second in 1 minute, the average response time is 14 ms.
1000 clients per second in 1 minute, the average response time is 15 ms.
1250 clients per second in 1 minute, the average response time is 259 ms.
1500 clients per second in 1 minute, the average response time is 1390 ms.
1750 clients per second in 1 minute, the average response time is 2020 ms.
2000 clients per second in 1 minute, the average response time is 2411 ms.
2500 clients per second in 1 minute, the average response time is 3131 ms.
3500 clients per second in 1 minute, the average response time is 4607 ms.
4500 clients per second in 1 minute, the average response time is 5992 ms.
5500 clients per second in 1 minute, the average response time is 7888 ms.
6500 clients per second in 1 minute, the average response time is 7723 ms.
7500 clients per second in 1 minute, the test was aborted because it reached the error threshold.
Load Test (Maintain client load) after enable Cache Enabler
From 0 to 250 clients in 1 minute, the average response time is 63 ms.
From 0 to 500 clients in 1 minute, the average response time is 196 ms.
From 0 to 750 clients in 1 minute, the average response time is 294 ms.
From 0 to 1000 clients in 1 minute, the average response time is 379 ms.
From 0 to 1250 clients in 1 minute, the average response time is 469 ms.
From 0 to 1500 clients in 1 minute, the average response time is 538 ms.
From 0 to 1750 clients in 1 minute, the average response time is 611 ms.
From 0 to 2000 clients in 1 minute, the average response time is 691 ms.
From 0 to 2500 clients in 1 minute, the average response time is 880 ms.
From 0 to 3500 clients in 1 minute, the average response time is 1208 ms.
From 0 to 4500 clients in 1 minute, the average response time is 1502 ms.
From 0 to 5500 clients in 1 minute, the average response time is 1837 ms.
From 0 to 6500 clients in 1 minute, the average response time is 1563 ms.
From 0 to 7500 clients in 1 minute, the average response time is 1790 ms.
From 0 to 8500 clients in 1 minute, the test was aborted because it reached the error threshold.
Note:Depending on the blog environment (plugins and various settings ), the load testing results will vary.
Speed Tests Results
GTmetrix:
PageSpeed Insights:
The speed optimization method can be summarized as: Cache Enabler + Cloudflare CDN
If you have any questions, please leave me a comment.