Works with your stack
Cookie consent for WP-Optimize
preloaded is not run, still
WP-Optimize caches pages, preloads scripts and delays them until the visitor moves. Two of those options touch consent. Both are off by default, and Cookie Rocks handles them when they are on.
By TeamUpdraft · teamupdraft.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
WP-Optimize - Clean, Compress, Cache
WordPress plugin
- Tested version
- 4.7.0
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 4.7.0 tested
- Active installs
- 1,000,000+
What WP-Optimize adds to your visitors’ browser
No trackers In our test of WP-Optimize - Clean, Compress, Cache 4.7.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 WP-Optimize
Preloading held trackers
With Preload JavaScript files on, WP-Optimize asks the browser to download every script early, a held Google tag included. The tracker does not run, but the request leaves. Cookie Rocks hides the address of held scripts from it.
Delay JS and the banner
Delay JS holds back every script until the first scroll or mouse move, a consent banner too. Cookie Rocks marks its scripts so they are never delayed.
One cached page for everyone
WP-Optimize serves the same cached file to every visitor, and a consent cookie does not change it. The choice is read in the browser. Cookie Rocks empties WP-Optimize’s page cache when its settings are saved.
What our tests found on WP-Optimize
Good to know · WP-OptimizeWhat WP-Optimize stores in visitors' browsers
WP-Optimize: 1 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for wpo_commented_postcookie Necessary Shows a commenter the page with their comment, outside the cache Read in its code, 2 November 2026, WP-Optimize.
Full detail
WP-Optimize can store these in a visitor's browser: wpo_commented_post (cookie, necessary: Shows a commenter the page with their comment, outside the cache). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Depends on a setting · WP-OptimizeWP-Optimize Delay JS can stop the consent banner from showing
setting “Delay JS” · by default: off
Delay JS holds every script until the first interaction, banners included, unless they carry its exclusion mark. Cookie Rocks 2.5.1 marks its scripts so they are never delayed.
Seen in our tests, 17 October 2026, WP-Optimize 4.7.0.
Full detail
With Delay JS on, WP-Optimize delays every script until the first interaction, consent banners included, unless they carry its exclusion attribute: a banner without it may not be shown or clickable. Cookie Rocks 2.5.1 marks its scripts so they are never delayed.
Depends on a setting · WP-OptimizeWP-Optimize preloading downloads held trackers before the choice
setting “Preload JavaScript files” · by default: off
With Preload JavaScript files on, the browser downloads held scripts such as Google's gtag.js early, without running them. Cookie Rocks 2.5.1 hides their address from it.
Seen in our tests, 17 October 2026, WP-Optimize 4.7.0.
Full detail
With Preload JavaScript files on, WP-Optimize adds a preload link for every script, so the browser downloads a held tracker (for example Google's gtag.js) before the choice, without running it. Cookie Rocks 2.5.1 hides the address of held scripts from it.
Depends on a setting · WP-OptimizeWP-Optimize Delay JS waits for scroll or mouse movement, not click or key
setting “Delay JS” · by default: off
There is no timeout, and scripts run one by one in page order. Its exclusion list checks script addresses only; a script written in the page needs the data-no-delay-js attribute.
Read in its code, 16 October 2026, WP-Optimize 4.7.0.
Full detail
WP-Optimize's Delay JS releases scripts only on the first scroll, mousemove, mouseover, resize, touchstart or touchmove, with no timeout and not on click or keydown; it moves each src to data-src, runs scripts one by one in document order, then dispatches fake DOMContentLoaded and load events. Its exclusion list compares src only, so an inline script can be kept out only with the data-no-delay-js attribute.
Good to know · WP-OptimizeWP-Optimize serves one cached file to every visitor
A consent cookie creates no separate version unless a developer adds it. Its only cookie, wpo_commented_post (1 week), follows a comment. Cookie Rocks 2.5.1 empties its cache on save.
Read in its code, 16 October 2026, WP-Optimize 4.7.0.
Full detail
WP-Optimize serves one cached file to every visitor; a consent cookie does not create a separate version unless a developer adds it with the wpo_cache_cookies filter. Its only cookie is wpo_commented_post (1 week, path of the post) after a visitor posts a comment, to skip the cache there. The free version adds no request to another site and has no WP Consent API or Consent Mode code. Cookie Rocks 2.5.1 empties WP-Optimize's page cache when its settings are saved.
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.
- WP-Optimize - Clean, Compress, Cache 4.7.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.
- Settings of the test: Default settings after activation.
- Last run: WP-Optimize - Clean, Compress, Cache 4.7.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
Does WP-Optimize set cookies of its own?
Only after a visitor posts a comment, to skip the cache on that post. The free version calls no other site.
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 WP-Optimize users
Fast pages, consent first.
wp-optimize stays on
Every feature of the complete plugin for 30 days, no card. WP-Optimize 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.