Works with your stack
Cookie consent for NitroPack
its own cookie, first page
NitroPack builds its optimized pages from a normal WordPress request, after the banner has rewritten them. The cached page carries nobody’s choice. Its footer script does set a cookie of its own on every page, before any choice.
By NitroPack · nitropack.io · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
NitroPack
WordPress plugin
- Tested version
- 1.20.4
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 1.20.4 tested
- Active installs
- 80,000+
What NitroPack adds to your visitors’ browser
Cookies seen in our test
nitroCachedPage
What matters for consent with NitroPack
Pages built after the banner
NitroPack’s optimizer requests your pages like a visitor, so trackers held by the banner are already held in the copy it stores. The choice stays in each visitor’s browser.
A cookie before the choice
NitroPack’s footer script sets a session cookie on every page before any choice. Some of its options add more: an impact test, a cache variation, and an affiliate cookie if a tracking parameter is configured. Check those options and list what they set in your cookie policy.
No consent signal of its own
NitroPack has no consent code. Cookie Rocks holds known trackers until consent, on NitroPack pages as on any other.
What our tests found on NitroPack
Good to know · NitroPackWhat NitroPack stores in visitors' browsers
NitroPack: 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 nitroCachedPagecookie Necessary Tells the site the page came from the NitroPack cache Seen in our tests, 2 November 2026, NitroPack.
Full detail
NitroPack can store these in a visitor's browser: nitroCachedPage (cookie, necessary: Tells the site the page came from the NitroPack 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.
Set before the choice · NitroPackNitroPack sets its cookies on every page before any choice
- nitroCachedPage (session) on every page.
- nitroImpactGroup (24 hours) with the impact test on.
- np_cache_variation (session) with the 304 option.
- cje (395 days, affiliate) on cached pages if cjevent is in its ignored parameters.
Read in its code, 16 October 2026, NitroPack 1.20.3.
Full detail
NitroPack's footer script sets the session cookie nitroCachedPage (1 or 0, SameSite=Lax) on every page before any choice. With the impact test on it sets nitroImpactGroup (24 hours); with the 304 option, np_cache_variation (session). If cjevent is in its ignored parameters, it copies it into a 395-day affiliate cookie cje on cached pages. Its footer also sends a sendBeacon and a periodic heartbeat to the site itself.
Good to know · NitroPackNitroPack caches the page rewritten by the consent plugin, with nobody's choice
NitroPack builds its page from a normal WordPress request. Cache is bypassed by default only for logged-in users and a few cookies, such as the cart's. It has no WP Consent API or Consent Mode code.
Read in its code, 16 October 2026, NitroPack 1.20.3.
Full detail
NitroPack builds its optimized page from a normal WordPress request made by its optimizer (X-Nitropack-Request header, Nitro-Optimizer-Agent), so the consent plugin's output buffer has already rewritten the HTML; with alwaysBuffer, NitroPack's buffer opens in advanced-cache.php and is outer. The cached page carries nobody's choice. Cache is bypassed by default only for logged-in users, comment_author, wp-postpass_ and woocommerce_items_in_cart. NitroPack has no WP Consent API or gtag('consent') code.
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.
- NitroPack 1.20.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: NitroPack 1.20.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
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 NitroPack users
Optimized pages, choices in the browser.
nitropack stays on
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.