faq
BotRefund and Your Site’s Performance: Load Speed & Core Web Vitals
Direct answer
BotRefund’s JavaScript snippet is designed to load quickly and run asynchronously, so it does not materially affect your page’s load speed or Core Web Vitals such as LCP, CLS, or FID.
How the script works
The snippet is injected into your site and monitors user interactions (click patterns, mouse movement, hidden‑element traps, etc.) after the page has begun rendering. Because it runs after the initial paint, the browser can display content to users without waiting for BotRefund to finish its checks.
Common mistake to avoid
Placing the BotRefund script synchronously in the <head> can block rendering and inflate metrics. Instead, add it just before the closing <body> tag or load it with async/defer attributes.
Verify the impact
- Run a performance audit (Lighthouse, PageSpeed Insights) before installing BotRefund.
- Install the script using the recommended async method.
- Run the audit again and compare LCP, FID, and CLS values. Any change should be negligible.
How BotRefund can help
BotRefund monitors a suite of signals—including ghost click detection, honeypot traps, and robotic pointer behavior—to identify non‑human traffic that inflates your Google and Meta ad spend. By flagging these bots, you can negotiate refunds and protect future campaigns.
Note: The service relies on client‑side signals, so extremely sophisticated bots that mimic human behavior may evade detection. Effective use also requires active ad spend on Google or Meta platforms.