Works with your stack
Cookie consent for Breeze
cached, delayed, still held
Breeze stores each page after the banner has done its work and serves it to every visitor who is not logged in. Its script delay leaves held trackers alone. Its video lazy loading is the part to watch.
By Cloudways · cloudways.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
Breeze
WordPress plugin
- Tested version
- 2.6.4
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 2.6.4 tested
- Active installs
- 300,000+
What Breeze adds to your visitors’ browser
No trackers In our test of Breeze 2.6.4 on 7 November 2026, the plugin itself added no tracker and no cookie. What you place in your pages with it, such as a video or a map, still counts.
What matters for consent with Breeze
One page, a banner for each visitor
No consent cookie creates a separate cached page in Breeze. The cached page keeps the Cookie Rocks banner, and each visitor makes their own choice in the browser.
Delayed scripts stay held
Breeze delays, groups and minifies only plain JavaScript. A script held by a banner is left untouched. Cookie Rocks also adds its own scripts to Breeze’s never-delay list, so the banner shows at once.
Lazy videos
With lazy loading of iframes on, Breeze rewrites embedded videos, which can stop a held Vimeo video from ever starting after consent. Cookie Rocks keeps known embeds out of Breeze’s list.
Cookies for logged-in users only
Breeze sets cookies only for logged-in users and after a comment. Anonymous visitors get none.
What our tests found on Breeze
Depends on a setting · BreezeDeactivating Breeze turns WP_CACHE off in wp-config.php
Breeze sets WP_CACHE to false in wp-config.php when it is deactivated. Check it before turning on another page cache.
What to do: After deactivating Breeze, check WP_CACHE in wp-config.php before enabling another page cache, or restore wp-config.php from a copy made before.
Seen in our tests, 23 October 2026, Breeze 2.6.3.
Full detail
When Breeze 2.6.3 is deactivated, it rewrites wp-config.php: it sets WP_CACHE to false and strips the file's blank lines. Another page cache plugin activated afterwards (WP Super Cache in our test) finds WP_CACHE off until its own setup runs again.
Good to know · Cookie RocksCookie Rocks works with four page caches on a real site
With WP Super Cache, W3 Total Cache, WP Fastest Cache or Breeze serving cached pages, each visitor still gets their own banner and choice.
Seen in our tests, 23 October 2026, Cookie Rocks 3.1.4 / 2.11.0 / 1.5.3 / 2.6.3.
Full detail
On a real site with the page cache of each plugin on and serving (cache marker in the page), the cached page keeps the Cookie Rocks head script and a single Google consent default, each visitor gets their own banner, one visitor's choice is never served to another, and the country rules endpoints answer 404 while the rules are off: WP Super Cache 3.1.4 (PHP mode, preload), W3 Total Cache 2.11.0 (Disk: Enhanced), WP Fastest Cache 1.5.3, Breeze 2.6.3. Three checks of three for each.
Depends on a setting · W3 Total Cache, BreezeW3 Total Cache and Breeze can remove WP Super Cache's .htaccess block
Trying W3 Total Cache or Breeze can remove WP Super Cache's block from .htaccess. Keep a copy of .htaccess before testing page caches.
What to do: Keep a copy of .htaccess before testing page caches and compare it afterwards.
Seen in our tests, 23 October 2026, W3 Total Cache, Breeze 2.11.0 / 2.6.3.
Full detail
On a real site, after W3 Total Cache 2.11.0 then Breeze 2.6.3 were each installed, enabled and removed, the '# BEGIN WPSuperCache ... # END WPSuperCache' block of an inactive WP Super Cache was gone from .htaccess: both plugins rewrite .htaccess. WP Super Cache in simple (PHP) mode keeps working without the block.
Depends on a setting · BreezeBreeze iframe lazy loading can stop held Vimeo videos from starting
setting “Lazy load iframes” · by default: off
With lazy loading of iframes on, Breeze rewrites embedded videos when its page cache serves them, which can stop a held Vimeo video from ever starting after consent. Cookie Rocks 2.5.1 keeps known embeds out of Breeze's list.
Seen in our tests, 17 October 2026, Breeze 2.6.2.
Good to know · W3 Total Cache, WP Super Cache, WP Fastest Cache, BreezeFour cache plugins keep the banner, and each visitor gets their own
setting “Page cache”
With W3 Total Cache, WP Super Cache, WP Fastest Cache or Breeze, the cached page keeps the Cookie Rocks banner. One visitor's choice is never served to another from the cache.
Seen in our tests, 17 October 2026, W3 Total Cache, WP Super Cache, WP Fastest Cache, Breeze 2.10.7, 3.1.4, 1.5.3, 2.6.2. Source
Full detail
With the page cache of W3 Total Cache (Disk: Enhanced), WP Super Cache (Simple mode), WP Fastest Cache or Breeze turned on, the page served from the cache keeps the Cookie Rocks banner, and each visitor gets their own banner: a choice made by one visitor is never served to another from the cache.
Good to know · BreezeBreeze serves the same cached page to visitors, whatever their consent
No consent cookie creates a variant or skips the cache. Breeze sets cookies only for logged-in users and after a comment (7 days). It has no consent signals.
Read in its code, 16 October 2026, Breeze 2.6.2.
Full detail
Breeze's page cache wraps the whole page from advanced-cache.php, so it stores the page after a consent plugin has rewritten it, the same for every visitor who is not logged in; no consent cookie creates a variant or bypasses the cache. Breeze sets cookies only for logged-in users (breeze_folder_name) and after a comment (breeze_commented_posts, 7 days). It has no WP Consent API or Consent Mode code.
See the 5 other findings
Good to know · BreezeBreeze's Delay All JavaScript kept trackers held with Cookie Rocks
In a test with 2.5.0, the tracker stayed held, the banner showed and the tracker ran after Accept all. The inline variant was not tested. Since 2.5.1 Cookie Rocks is on Breeze's never-delay list.
Seen in our tests, 16 October 2026, Breeze 2.6.2.
Full detail
In a test with Breeze's Delay All JavaScript (Expert preset) and Cookie Rocks 2.5.0, the held tracker stayed held, the banner appeared and the tracker ran after Accept all. The Delay JS inline scripts variant was not tested. Since 2.5.1 Cookie Rocks also adds its own scripts to Breeze's never-delay list (filter default_scripts_gnore_from_delay).
Good to know · BreezeBreeze leaves held scripts untouched and never delays Google tags
Breeze only minifies, groups and delays normal scripts, so a script held as text/plain is left alone. Delay All JavaScript never delays scripts that contain Google tag code.
Read in its code, 16 October 2026, Breeze 2.6.2.
Full detail
Breeze minifies, groups and delays only scripts with no type or a JavaScript type: a script held as text/plain is left untouched. Delay All JavaScript recreates delayed scripts at DOMContentLoaded and never delays scripts containing gtag(, ga( or googletagmanager.com. Breeze reads no no-optimize attribute, and the default list of 'Delay JS inline scripts' (off by default) contains data-noptimize and gtag.
Good to know · BreezeBreeze does not cache pages for non-browser visitors
Breeze does not cache pages requested with a non-browser user agent (for example node) or with the header Accept-Language: *. A cache test that does not send a real browser user agent sees no cached page at all.
Seen in our tests, 15 October 2026, Breeze 2.6.2.
Good to know · Cookie Rocks ProCookie Rocks Pro clears page caches when an update changes banner values
It clears the caches of seven known plugins, such as WP Rocket and LiteSpeed Cache, at the first request after the update. Host and CDN caches keep the old pages until they expire.
What to do: After an update that changes banner defaults, clear the host or CDN cache by hand.
Read in its code, 15 October 2026, Cookie Rocks Pro.
Full detail
When an update of Cookie Rocks Pro changes or removes a value it sends to visitors (for example the default accent colour), Pro clears the known page caches (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, SiteGround Optimizer, WP Fastest Cache, Breeze) at the first request after the update, with no extra database query and nothing more for visitors. An added value clears nothing. Host and CDN caches are not cleared and keep the old pages until they expire.
Good to know · WP Fastest Cache, BreezeCookie Rocks Pro clears WP Fastest Cache and Breeze page caches on save
Also when an update changes a default sent to visitors. Breeze's purge also clears its minified files and object cache, and Varnish or Cloudflare only if set up in Breeze.
Seen in our tests, 15 October 2026, WP Fastest Cache, Breeze 1.5.3 (WP Fastest Cache), 2.6.2 (Breeze).
Full detail
Cookie Rocks Pro clears the page caches of WP Fastest Cache (wpfc_clear_all_cache, pages only) and Breeze (action breeze_clear_all_cache) when its settings are saved and when an update changes a default sent to visitors. Breeze's purge also clears its minified files and its object cache; it purges Varnish and Cloudflare only if they are set up in Breeze, with no extra network request otherwise.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- Breeze 2.6.4, tested on 7 November 2026.
- The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
- Settings of the test: Default settings after activation.
- Last run: Breeze 2.6.4 on 7 November 2026, with WordPress 7.1.3.
Light as a pebble
11.43 kB once, 1.00 kB per page. Measured, not promised.
lighter than the font on this page*
Every kilobyte costs your visitors time and costs you Core Web Vitals. Cookie Rocks adds 11.43 kB to the first page a visitor opens, then 1.00 kB to each page after that, because its files stay in the browser cache. It calls no outside server and never shifts your layout.
11.43 kB First visit, in total
1.00 kB Each next page
7.74 kB JavaScript, first visit
3.48 kB Stylesheet, first visit
0 Requests to other servers
0 Layout shift caused
* The font on this page is Inter, compressed and cut down to the Latin alphabet. It still weighs 26.23 kB.
Page cache
Other plugins of the same kind.
Questions
Why does my cache test show no cached page?
Breeze does not cache requests from a tool that does not send a real browser user agent. Test with a normal browser.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For Breeze users
Cached pages, held trackers.
breeze stays on
Every feature of the complete plugin for 30 days, no card. Breeze keeps working as it does today.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.