Works with your stack
Cookie consent for W3 Total Cache
left as it is
W3 Total Cache minifies and caches nearly everything: pages, scripts, styles, database queries. The consent tags need to reach the browser exactly as written.
By BoldGrid · boldgrid.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
W3 Total Cache
WordPress plugin
- Tested version
- 2.11.0
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 2.11.0 tested
- Active installs
- 900,000+
What W3 Total Cache adds to your visitors’ browser
No trackers In our test of W3 Total Cache 2.11.0 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 W3 Total Cache
Minify
W3 Total Cache can minify scripts and the tags written in the page. A consent script changed on the way may stop working.
Several caches
Page, object, database and browser caches each keep their own copy. A banner change has to clear them.
A CDN
W3 Total Cache can send files to a CDN. A CDN set up outside the plugin keeps its own copy.
Browser cache
W3 Total Cache can tell browsers to keep files for a long time. Files that change name with their content are never served stale.
Cookie Rocks with W3 Total Cache
- Adds the banner’s scripts to its exclusions from delay, combining and minifying.
- Clears its page cache when you change something visitors can see.
What our tests found on W3 Total Cache
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.
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 · W3 Total CacheW3 Total Cache lazy loading skips videos; Delay Scripts delays only listed ones
Lazy loading handles images only, so an embedded video keeps its address. Delay Scripts (Pro) waits for the first key, mouse, touch or wheel action, or 5 seconds by default.
Read in its code, 16 October 2026, W3 Total Cache 2.10.7.
Full detail
W3 Total Cache's lazy loading only handles images (<img>, <picture>), never iframes or videos, so an embedded video keeps its src. Delay Scripts, a Pro feature, only delays the scripts the administrator lists, until the first keydown, mouseover, touchmove, touchstart or wheel, or a timeout (5,000 ms by default).
Depends on a setting · W3 Total CacheW3 Total Cache's auto minify can run a held script before the choice
setting “Minify: JS minify, auto mode” · by default: off
It combines local scripts into one file whatever their type, so a script held by a consent plugin can run before the choice. Only its ignore list or a filter excludes a script.
Read in its code, 16 October 2026, W3 Total Cache 2.10.7.
Full detail
With automatic JavaScript minify, W3 Total Cache takes every local <script src> out of the page and combines it into a minified file whatever its type, except module, importmap and application/json. A local script held as type="text/plain" by a consent plugin can therefore end up in the combined file and run before the choice. External scripts are combined only if their caching is enabled. No attribute on the tag excludes it: only the ignore list or the w3tc_minify_js_do_tag_minification filter returning false.
Good to know · W3 Total CacheW3 Total Cache sets no cookie for anonymous visitors by default
- w3tc_logged_out (session, at logout) and w3tc_logged_<role hash> for excluded roles.
- w3tc_preview for the admin preview.
- w3tc_referrer (session) only when a referrer group is enabled.
- No third-party host on visitor pages; its usage tracking runs in the admin, off by default.
Read in its code, 16 October 2026, W3 Total Cache 2.10.7.
Full detail
W3 Total Cache sets no cookie for ordinary anonymous visitors by default. Its cookies are w3tc_logged_out (session, at logout), w3tc_logged_<role hash> (logged-in users of an excluded role), w3tc_preview (admin preview) and, only when a referrer group is enabled, w3tc_referrer (session, set on the first page from another site). It adds no third-party host to visitor pages by default; its Google Analytics usage tracking runs in the admin only and is off unless the administrator agrees. It does not use WP Consent API and sets no Consent Mode default.
See the 3 other findings
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 · LiteSpeed Cache, W3 Total Cache, SiteGround Optimizer, AutoptimizeCache plugins' JavaScript options keep the Cookie Rocks banner first
With LiteSpeed Cache, W3 Total Cache, SiteGround Optimizer or Autoptimize combining or delaying scripts, the banner script stays first and untouched, and trackers are held until Accept all.
Seen in our tests, 15 October 2026, LiteSpeed Cache, W3 Total Cache, SiteGround Optimizer, Autoptimize 7.9.1, 2.10.7, 7.8.4, 3.1.16.
Full detail
With JavaScript combined, minified or delayed (LiteSpeed Cache including Guest Mode and Load JS Delayed, W3 Total Cache minify in auto mode, SiteGround Optimizer combine and async, Autoptimize aggregate including inline JS), the Cookie Rocks head script stays first and untouched, its engine stays a separate file, and trackers are held until Accept all. Without a LiteSpeed web server, LiteSpeed Cache sets no cookie.
Good to know · W3 Total CacheW3 Total Cache minify and browser cache keep the banner and holding working
setting “Minify JS (auto) ; Browser cache”
The Cookie Rocks head script stays first and trackers are held until Accept all. Cookie Rocks files are cached for a year, but their addresses change with each version and banner text.
Seen in our tests, 15 October 2026, W3 Total Cache 2.10.7.
Full detail
With W3 Total Cache's JavaScript minify (auto mode) on as well as the page cache, the page's scripts are combined into one file; the Cookie Rocks head script stays first and untouched, the engine stays separate, and the trackers are held until Accept all. With its browser cache on, Cookie Rocks files are kept for a year, but their addresses change with each version and with the banner texts, so visitors never get stale texts.
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.
- W3 Total Cache 2.11.0, 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.
- With its page cache switched on, each visitor still gets the banner in the right state.
- Settings of the test: Page cache turned on (Disk: Enhanced).
- Last run: W3 Total Cache 2.11.0 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
Will visitors see each other’s choices in a cached page?
No. The choice is read in the browser, after the page arrives, so the cached page is the same for everyone.
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 W3 Total Cache sites
Keep your caches, add consent.
left as it is
Every feature of the complete plugin for 30 days, no card.
- 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.