Cookie consent for WP Fastest Cache

What WP Fastest Cache adds to your visitors’ browser

What matters for consent with WP Fastest Cache

What our tests found on WP Fastest 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.

• 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.

• Depends on a setting · WP Fastest CacheWP Fastest Cache Combine JS can run held trackers before the choice

  setting “Combine JS” · by default: off

  With Combine JS on, the site's head scripts are merged into one file, so a held tracker can run from it. Cookie Rocks 2.5.1 keeps held scripts out of the merged file.

  Seen in our tests, 17 October 2026, WP Fastest Cache 1.5.3.

  Full detail

  With Combine JS on, WP Fastest Cache merges the site's own scripts in the page head into one file, whatever their type, so a tracker held by a banner can run from the merged file before the choice. Cookie Rocks 2.5.1 keeps held scripts out of the merged file.

• Good to know · WP Fastest CacheWP Fastest Cache serves one cached page to every visitor, whatever the choice

  It stores the page already rewritten by the consent plugin, and no consent cookie bypasses its cache by default. The free version sets no cookie and adds no third-party request.

  Read in its code, 16 October 2026, WP Fastest Cache 1.5.3.

  Full detail

  WP Fastest Cache opens its output buffer when the plugin loads, outside a consent plugin's buffer opened at template_redirect, so it stores the page already rewritten by the consent plugin and serves the same file to every anonymous visitor (via .htaccess or PHP). No consent cookie bypasses its cache by default; a $consent_cookie variable in its rules is always empty. The free version sets no cookie and adds no third-party request on visitor pages, and it does not use WP Consent API or Consent Mode. It refuses to enable its cache while one specific consent plugin is active.

• Depends on a setting · WP Fastest CacheWP Fastest Cache's CDN option also rewrites addresses in data attributes

  setting “CDN” · by default: off

  A local address in data-src or a consent plugin's attribute (such as data-cr-src) is moved to the CDN host too. YouTube or Vimeo embeds are not affected.

  Read in its code, 16 October 2026, WP Fastest Cache 1.5.3.

  Full detail

  With a CDN set in WP Fastest Cache, its cdn_rewrite looks for src= without a word boundary, so a local address kept in data-src or in a consent plugin's data attribute (such as data-cr-src) is rewritten to the CDN host too. External embeds such as YouTube or Vimeo are not affected.

• 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.

Page cache

Other plugins of the same kind.

Every plugin and theme we test →