Works with your stack
Cookie consent for Hummingbird
combined files hide addresses
Hummingbird sets no cookie on visitor pages, and its page cache serves the same page to every anonymous visitor. Its asset optimization is what needs care: it can combine a tracker into a file a banner no longer recognises, and delay the banner itself.
By WPMU DEV · wpmudev.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
Hummingbird
WordPress plugin
- Tested version
- 4.0.0
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 4.0.0 tested
- Active installs
- 70,000+
What Hummingbird adds to your visitors’ browser
No trackers In our test of Hummingbird 4.0.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 Hummingbird
Combined files lose their address
Hummingbird combines scripts before the page is written. A tracker served from your own site can end up in a Hummingbird file, under an address no banner recognises. Exclude trackers from combining.
The banner must not wait
Delay JavaScript leaves held scripts alone, but it also delays the banner’s own scripts until the first gesture. Exclude the banner’s scripts from the delay.
A CDN from WPMU DEV
With the WPMU DEV CDN on, optimized files load from WPMU DEV’s servers, so visitors’ browsers contact them.
The same cached page for all
A consent cookie does not create a separate cached page. The choice is read in the browser, so the cached page fits everyone.
What our tests found on Hummingbird
Good to know · HummingbirdHummingbird can combine a tracker or the banner into its own files
A tracker combined into a Hummingbird file has an address a banner does not recognise, and the banner's script can be combined, deferred or moved. Filters such as wphb_dont_combine_handles exclude it.
Read in its code, 16 October 2026, Hummingbird 3.21.2.
Full detail
Hummingbird's free Asset Optimization works on WordPress script handles (print_scripts_array, priority 5) before any output buffer: a locally enqueued tracker can be combined into a Hummingbird file, whose address a banner does not recognise, and a banner's own handle can be combined, deferred or moved to the footer. Filters such as wphb_dont_combine_handles exclude a handle. With the WPMU DEV CDN, files come from hb.wpmucdn.com.
Depends on a setting · HummingbirdHummingbird's Delay JavaScript makes the banner wait unless excluded
setting “Delay JS” · by default: off
Off by default. Held scripts stay held, but the banner's own scripts wait for the first key, mouse, wheel or touch event, or 20 seconds, unless excluded (wphb_delay_js_exclusions).
Read in its code, 16 October 2026, Hummingbird 3.21.2.
Full detail
Hummingbird's Delay JavaScript (off by default, WPMU DEV members) rewrites each script to type="wphb-delay-type" in a buffer opened at template_redirect priority 2, so it runs after a banner's later buffer and leaves held type="text/plain" scripts untouched. It reads no common no-delay attribute, so a banner's own scripts wait for the first key, mouse, wheel or touch event or 20 seconds unless excluded (wphb_delay_js_exclusions, wphb_should_delay_js, WPHBDONOTDELAYJS).
Good to know · HummingbirdHummingbird serves the same cached page whatever the consent cookie
It sets no cookie and stores nothing in the browser. Its page cache is written after the banner's processing, and a consent cookie does not create a separate version.
Read in its code, 16 October 2026, Hummingbird 3.21.2.
Full detail
Hummingbird sets no cookie and stores nothing in the browser on visitor pages. Its page cache serves the same page to every anonymous visitor, written after the banner's processing; only wp-postpass_, comment_author_, wordpress_logged_in_ and wphb_cache_* cookies create variants, so a consent cookie does not. It has no iframe lazy loading (only comments).
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.
- Hummingbird 4.0.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: Hummingbird 4.0.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
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 Hummingbird users
Optimized assets, consent first.
hummingbird 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.