Skip to content

Works with your stack

Cookie consent for FlyingPress

keywords, not attributes

← Cookie Rocks for your stack

FlyingPress caches your pages and can defer scripts, or delay them until the visitor interacts. It reads no attribute in a script tag, so a consent script stays out of the delay only through keywords or filters.

By Gijo Varghese · flyingpress.com

Is this your product? Tell us if anything here is out of date. Write to us

What matters for consent with FlyingPress

No attribute is read

FlyingPress does not look for an attribute on a script to leave it alone. It skips a script only when a keyword matches the whole tag: its address, its id or its inline code.

Filters for other plugins

FlyingPress added filters so that other plugins can keep their scripts out of the delay and the defer. Cookie Rocks hooks them when FlyingPress is installed. FlyingPress is a paid plugin with no public code: the filters come from its documentation and changelog, and have not been tried on a real site yet.

A keyword of your own

If the banner appears only after the first scroll or click, add cookie-rocks to the exclusions of « Delay all JavaScript ». Keywords have no wildcard, so a short exact word is enough.

One cached page for everyone

FlyingPress serves the same cached page to every visitor. The choice is read in the browser after the page arrives, so the cached page never holds one visitor’s choice.

Its own cookies

The FlyingPress changelog names no cookie for visitors. It mentions a cookie for the roles of logged-in users; its name and duration are not documented.

Light as a pebble

10.25 kB once, 1.13 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 10.25 kB to the first page a visitor opens, then 1.13 kB to each page after that, because its files stay in the browser cache. It calls no outside server and never shifts your layout.

10.25 kB First visit, in total

1.13 kB Each next page

10.03 kB JavaScript, first visit

In the script 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.

Questions

Do I need to exclude anything after an update of FlyingPress?

FlyingPress says its delay no longer needs exclusions in recent versions. A consent script has to run before the scripts it holds, so keep the cookie-rocks keyword if the banner is late.

Will visitors see each other’s choices in a cached page?

No. The choice is read in the browser, after the page arrives, so the cached page is the same for everyone.

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 FlyingPress sites

Keep FlyingPress, add consent.

consent before the delay

Every feature of the complete plugin on your FlyingPress site 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

How the trial works, in detail

Cookie Rocks

Get your trial key

Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.

One trial per domain. Local and staging sites never use up your key.

We keep your e-mail address to send your key and help you with it, as explained in our privacy policy. No newsletter, nothing else.