This setting allows you to manually delay selected scripts until the user interacts with the page (scrolls, clicks, taps). It gives you full control over which scripts are delayed, especially those not auto-detected by FlyingPress.
How It Works
Scripts matching the specified keywords in their URLs or filenames will be delayed.
These scripts will not load or execute until the user interacts with the page.
Useful for self-hosted or inline scripts, or when more granular control is needed.
Common Third-party Scripts to Delay
Here are some commonly used third-party scripts you can consider delaying:
googletagmanager.com
google-analytics.com
googleoptimize.com
adsbygoogle.js
xfbml.customerchat.js
fbevents.js
widget.manychat.com
cookie-law-info
grecaptcha.execute
static.hotjar.com
hs-scripts.com
embed.tawk.to
disqus.com/embed.js
client.crisp.chat
matomo.js
usefathom.com
code.tidio.co
metomic.io
js.driftt.com
cdn.onesignal.com
clarity.ms
Best Practices
Only delay scripts that are non-essential during initial page load (e.g., analytics, chat, ads).
Do not delay scripts required for above-the-fold UI (e.g., sliders, menus).
Use specific keywords to avoid over-matching.
Always test your site after applying delay rules to ensure nothing breaks.