This article contains affiliate links. AutomateWithMNK may earn a commission if you sign up through certain links, at no additional cost to you. This does not influence our editorial assessment.
Speed up WordPress on Cloudways: the short method
On Cloudways, WordPress speed is tuned in layers, in this order: one page cache (Breeze, Cloudways’ own plugin, which works with Varnish), an object cache (Redis, or Object Cache Pro included on Flexible), the server stack (the NGINX and PHP-FPM based Lightning Stack), then a CDN for distant visitors. Measure before and after each layer; without measurements, a setting can just as easily slow you down.
This guide relies on Cloudways’ official pages and Breeze’s WordPress.org listing, . It promises no specific gain: AutomateWithMNK has not measured a site on Cloudways, and Cloudways’ own claims are labelled as such.
Visit Cloudways and start the free trial
Running a store? Also read Cloudways for WooCommerce.
Take a baseline first
Pick three representative pages: the home page, an image-heavy page and a dynamic page such as search, account or cart. Measure each several times with the same tool at similar hours and keep the median. Repeat after every change, one change at a time, so you know what actually helped.
What each layer does
| Layer | What it speeds up | On Cloudways |
|---|---|---|
| Page cache | Pages identical for every visitor | Breeze, with Varnish support |
| Object cache | Repeated database queries, dynamic pages included | Redis; Object Cache Pro included on Flexible |
| Stack | PHP execution and file serving | Lightning Stack (NGINX and PHP-FPM) |
| CDN | Static files for distant visitors | Cloudflare Enterprise add-on from $4.99 per domain per month |
| Browser cache | Repeat visits | Breeze option |
Tuning Breeze safely
Breeze, built by Cloudways, offers file-level caching, HTML, CSS and JavaScript minification, Gzip, browser caching, lazy-loaded images, database clean-up, CDN integration, Heartbeat API control, exclusions and preloading. Switch them on in stages:
- Page cache and Gzip first, the lowest-risk settings.
- Lazy loading next, checking that images display.
- Minification last, one file type at a time. On Breeze’s listing, users report that JavaScript minification stopped charts from loading, and one store had to keep several options off.
- Exclusions for dynamic pages. The listing notes that when Varnish is active, exclusions must also be set in the Varnish configuration, not only in Breeze.
Above all, Breeze’s listing advises against running two caching plugins at once. Disable any other cache plugin before enabling it.
Turning on object caching
An object cache keeps frequent database results in memory. It mainly helps the pages a page cache cannot serve: cart, account, search and the admin area. On Cloudways Flexible, the pricing page lists Redis and Object Cache Pro as free. Enable it in the application settings, then check that admin and dynamic pages respond faster.
Moving to the Lightning Stack
The Lightning Stack is the NGINX and PHP-FPM based stack Cloudways now promotes. Its homepage claims “up to 65% faster load times”, measured by Cloudways against its previous hybrid stack, which makes it a vendor claim. According to the launch post, you switch in Application Settings, Stack Setting tab, Lightning option, then Update Now. List your .htaccess rules first: the Lightning Stack does not read them, as the changelog also confirms.
Adding a CDN
A CDN serves images, stylesheets and scripts from servers close to visitors, which matters most when your audience is far from your server’s region. Breeze offers CDN integration, and Cloudways sells Cloudflare Enterprise as an add-on.
Common pitfalls
- Two caching plugins active at once.
- Minification switched on for every file type at once.
- Exclusions set in Breeze but forgotten in Varnish.
- Switching to the Lightning Stack before rebuilding .htaccess rules.
- Resizing the server before tuning caching.
Tuning order
| Step | Change | Check |
|---|---|---|
| 1 | Baseline measurements | Median of three pages |
| 2 | One page cache (Breeze), Gzip | Pages served from cache |
| 3 | Object cache | Faster admin and dynamic pages |
| 4 | Lightning Stack, after rebuilding .htaccess rules | Redirects intact |
| 5 | Lazy loading, then minification per file type | Layout and features intact |
| 6 | CDN if visitors are far away | Static files served by the CDN |
| 7 | Server size, if load stays high | Load under control at busy hours |
Try these settings during a Cloudways trial
FAQ
Should I use Breeze or another caching plugin?
Breeze comes with Cloudways and supports Varnish; another plugin is possible, but never two at the same time.
Does the Lightning Stack make sites faster?
Cloudways says so, using its own measurements against its previous stack. Measure your site before and after switching.
Is object caching extra?
Not on Flexible: the pricing page lists Redis and Object Cache Pro as free.
Do I need a CDN?
Mostly when visitors are far from your server’s region; for a nearby audience the gain is smaller.
Sources
Pages checked on .
- Breeze on WordPress.org (features, Varnish, caveats, reviews)
- Lightning Stack launch post and changelog
- Cloudways homepage (performance claim)
- Cloudways pricing page (Redis, Object Cache Pro, Cloudflare Enterprise)
