Works with your stack
Cookie consent for Flying Scripts
pick keywords with care
Flying Scripts delays only the scripts that match your keywords, and it never touches a script held by a banner. It sets no cookie and calls no other site. The one risk is a keyword that is too broad.
By WP Speed Matters · wpspeedmatters.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
Flying Scripts
WordPress plugin
- Tested version
- 1.2.5
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 1.2.5 tested
- Active installs
- 30,000+
What Flying Scripts adds to your visitors’ browser
No trackers In our test of Flying Scripts 1.2.5 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 Flying Scripts
Held scripts stay held
Flying Scripts delays plain JavaScript only. A script held by a consent plugin keeps waiting for the choice.
“gtag” catches too much
The keyword “gtag” also matches the banner script that sets Google’s default consent. That script would then wait for the first interaction, after the trackers it should govern. Use a precise address such as googletagmanager.com/gtag/js instead.
Nothing to exclude by attribute
Flying Scripts has no exclusion attribute. The keyword list is the only control, so keep it short and exact.
What our tests found on Flying Scripts
Depends on a setting · Flying ScriptsFlying Scripts' gtag keyword can also delay the banner's consent script
setting “Include keywords (flying_scripts_include_list)” · by default: empty
The keyword also matches the consent plugin's own head script, so Google's default consent would wait for the first interaction, and delayed scripts run in no set order.
What to do: Use a precise address such as googletagmanager.com/gtag/js as the keyword.
Read in its code, 16 October 2026, Flying Scripts 1.2.5.
Full detail
The keyword "gtag" suggested in Flying Scripts' FAQ also matches any inline script containing that word, such as a consent plugin's head script that sets Google's default consent: it would wait for the first interaction, and delayed scripts run with no guaranteed order. Flying Scripts has no exclusion attribute or filter.
Good to know · Flying ScriptsFlying Scripts never touches scripts held by a consent plugin
setting “Include keywords (flying_scripts_include_list)” · by default: empty
By default it delays nothing. It only delays ordinary scripts matching its keywords, until the first interaction or 5 seconds. It sets no cookie and adds no third-party request.
Read in its code, 16 October 2026, Flying Scripts 1.2.5.
Full detail
Flying Scripts only delays scripts whose tag matches one of its keywords (empty list by default, so nothing is delayed), and only scripts with no type or type text/javascript: a script held by a consent plugin as type="text/plain" is never touched. Its output buffer opens at plugin load, so it rewrites the page after a banner's later buffer. Delayed scripts run on the first click, mouse move, key, touch or wheel, or after 5 seconds. It sets no cookie and adds no third-party request.
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.
- Flying Scripts 1.2.5, 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: Flying Scripts 1.2.5 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.
Optimisation
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 Flying Scripts users
Delayed scripts, consent first.
flying scripts 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.