Breeze Cache Plugin 2.5.16 Tested Under Real WordPress Traffic

Every WordPress website eventually has a moment where more visitors show up than it’s used to handling. 

What happens in that moment depends entirely on what’s running under the hood. We wanted to know exactly what that moment looks like with Breeze, Cloudways’ free WordPress caching plugin, running on a website, and what it looks like without it. So instead of guessing, we tested it directly, and we’re walking through the actual numbers here so you know exactly what they mean for your own website. 

The Result, Up Front

Without any caching plugin running, the test website’s average response time under a realistic traffic rush stretched past 20 seconds, and the server could only handle a handful of visitors per second before falling behind.

With Breeze 2.5.16 active, the same website handled up to 38 times more traffic per second, cut response times down to a fraction of a second to a few seconds, and didn’t drop a single request across nine separate test runs. 

How We Tested This

We took a live WordPress website and simulated 32 visitors trying to load the homepage at the exact same moment, continuously, for a full minute. That’s a reasonable stand-in for a real traffic spike generated by enough concurrent visitors to expose whether a website holds up or starts to buckle.

To make sure we weren’t reporting a fluke, we didn’t run this once. We used three separate, independently built testing tools and ran each one three times, comparing the same website with no caching plugin against the same website running Breeze 2.5.16. That’s nine total test runs per condition. This set of multiple runs allowed us to identify and dismiss noise and only use data that is consistent for the purpose of this test.

What “Requests Per Second” Means, and What We Found

When a testing tool reports requests per second, it’s measuring how many separate visitors could load the page within that same one-second window without the server falling behind. In practical terms, this is the number that determines whether your website survives a WordPress traffic spike, whether that’s a sales campaign, a newsletter blast, or a post that unexpectedly goes viral.

Without any caching plugin active, our test website could only handle somewhere between 1 and 4 requests per second, depending on which tool measured it. That’s barely enough capacity for two or three subscribers clicking through an email campaign at the same moment. If your list is any larger than that, or a sale or announcement drives even modest traffic within the same minute, requests start queuing up and pages start timing out for everyone who arrives after the first few visitors.

With Breeze switched on, that number jumped to somewhere between roughly 9 and 70 requests per second, depending on the tool. In this case, the website can easily handle the increased number of visitors landing on your product pages during sales rush. 

Why this matters for your website

This is the number that matters most if your traffic doesn’t arrive in a steady pattern. Most WordPress websites don’t get predictable, evenly spaced visitors. They get spikes, and the requests-per-second figure is what actually tells you whether your website can absorb one or whether it buckles the moment a handful of people show up at once. 

What “Average Response Time” Means, and What We Found

This one is more intuitive because it’s really just page load time: how long a visitor stares at a blank or half-loaded page before anything shows up.

Without caching, average response time during our test stretched to somewhere between 20 and 23 seconds. This is a critical value because most visitors give up well before the 5-second mark, and industry data consistently shows abandonment climbing sharply after just 3 seconds.

With Breeze switched on, that number jumped to somewhere between roughly 9 and 70 requests per second, depending on the tool. In this case, the website can easily handle the increased number of visitors landing on your product pages during sales rush. 

Why this matters for your website

If your website already feels fast during a normal, quiet afternoon, that can be misleading. The real test is what happens the moment several visitors show up together, and that’s precisely the gap this number is measuring. 

What “Zero Failures” Really Means

Across every single test run, we tracked how many requests came back as errors or timeouts instead of a successful page load.

With Breeze running, that number was zero, with not one visitor was shown an error page or a stalled request, even at the peak of the test.

A slow website frustrates visitors. A website that starts throwing errors under load actively turns them away, at the exact moment interest in the website is highest.

Why This Happens

Every time someone loads a WordPress page without caching, the server rebuilds that page from scratch by pulling content from the database, running the theme’s code, and assembling the whole thing as the webpage they see in their browser. That’s fine when a handful of people visit across a day. However, it falls apart fast when thirty people arrive in the same minute, because the server ends up repeating that same expensive rebuilding work over and over while new visitors keep piling up behind it.

Caching solves this by saving a finished, ready-to-serve copy of the page the first time it’s built, so every visitor after that gets handed the same fast copy instead of making the server start from zero again. That’s the entire mechanism behind Breeze, a free WordPress caching plugin built specifically for Cloudways hosting, and it’s why the gap under real load is this large rather than a modest improvement .

Checking Our Work With Independent, Third-Party Tools

Load testing shows what happens under pressure, but it’s worth also checking what a single, ordinary visitor experiences on a completely normal page load, with no traffic spike involved at all. 

For that, we ran the Breeze-enabled website through Google’s PageSpeed Insights and GTmetrix, two of the most widely trusted independent scanning tools. Note that neither tool has any connection to Cloudways or Breeze. They’re the same free, publicly available tools used to check the speed of any website on the internet, which is exactly why anyone reading this can run the same scan on their own website and compare website performance.

With Breeze active, the website scored 95 out of 100 on desktop and 81 out of 100 on mobile in PageSpeed Insights, and 96% in GTmetrix’s Performance grade.

A few of the specific numbers behind those scores are worth understanding on their own:

Largest Contentful Paint, 1.1 seconds, measures how long it takes for the biggest visible thing on the page, usually a hero image or main headline, to actually appear. This is the number that most closely matches what a visitor would describe as “how fast did this feel,” and Google considers anything under 2.5 seconds good.

Total Blocking Time, 2 milliseconds, measures whether the page freezes or stutters while it finishes loading, the kind of thing you notice when you try to tap something and nothing happens for a moment. A number this low means the page stays responsive the entire time it’s loading.

Cumulative Layout Shift, 0, measures whether elements on the page jump around as it loads, like text shifting just as you’re about to tap a button. A score of 0 means nothing moves unexpectedly.

These three numbers matter beyond just feel because Largest Contentful Paint and Cumulative Layout Shift are two of Google’s three Core Web Vitals used as ranking signals in search results. A website that scores well here isn’t only faster for visitors, it’s also positioned to perform better in search, since Google explicitly factors these into how pages rank.

What This Means for Your Website

If you’re running a WordPress website, ask yourself one direct question: what happens right now if 20 or 30 people land on the same page within the same minute? For a large share of WordPress websites, the honest answer is that response times climb sharply and some visitors start seeing errors.

That’s the exact scenario this benchmark tested, on both the pressure side and the everyday side. Under a traffic spike, Breeze took a website from response times measured in tens of seconds down to a fraction of a second to a few seconds, without dropping a single request. Under normal conditions, that same website scored in the “good” range on the same independent tools used across the industry to judge website speed.

It is important to disclose that Cloudways servers already run Varnish in the background as the cache layer. The numbers above isolate what Breeze itself adds on top of a standard WordPress setup. 

Breeze, Cloudways’ free WordPress caching plugin, is already built into Cloudways hosting, and based on what we measured, it’s doing real, verifiable work in both situations 

FAQ

Do I need to install Breeze myself, or is it already on my site?

If you’re hosting on Cloudways, Breeze typically comes pre-installed and pre-activated with default settings on new Optimized WordPress applications. Alternatively, you can install it on your WordPress website from the official WOrdPress Plugin repository from WordPress Admin > Plugins > Add New Plugin.

Is Breeze really free, or are there paid tiers?

Breeze is completely free, with no premium upsell. It’s included at no extra cost with Cloudways hosting.

Does Breeze work with WooCommerce and other plugins?

Yes. Breeze is built to work with WooCommerce and WordPress Multisite, and it’s tested for compatibility with popular WordPress.org plugins.

My Cloudways server already runs Varnish. Do I still need Breeze?

Varnish caches pages at the server level regardless of which WordPress plugin is active, but Breeze adds WordPress-level optimizations on top of that, like database cleanup, minification, and browser caching, that Varnish alone doesn’t handle.

What tools did you use for this benchmark?

Three independent load-testing tools, Oha, k6, and JMeter, each run three separate times, plus GTmetrix for independent, real-world scoring.

Will Breeze slow down my WordPress admin or editing experience?

No. Caching applies to how pages are served to visitors, not to how you work in the dashboard, so editing and publishing aren’t affected.

[email protected]

Zafar Iqbal is a Senior Technical Writer who's spent the last decade making server products, WordPress, and SaaS platforms actually make sense to people. As someone who lives at the intersection of tech and marketing, he loves turning complicated technical concepts into insights that help people make the right business decisions. When he's not demystifying managed hosting infrastructure, he's tinkering with his hobby projects.

Get Connected on: Twitter Community Forum