Table of Contents
| Technique | Effect |
|---|---|
Minified trackers loaded with defer | No render-blocking JavaScript |
| Batched sending | A few small requests instead of one per event |
| Recorder (Pro) starts after load or first interaction, record-only build (~68 KB) | No impact on first display |
| Hybrid Storage | Bulky data in files, lean database |
| Background jobs in small batches | Migrations and cleanup never block a page |
| Pre-aggregated, cached dashboard widgets | Fast admin even with big data |
| Licence checks back off when the server is unreachable (Pro) | No slow pages if a firewall blocks outbound calls |
Measure it yourself #
- Run Lighthouse or PageSpeed Insights before and after activating.
- Check the trackers carry
deferin the page source. - Watch Settings → Storage Stats over a few weeks.
FAQ #
Does it add database load on busy sites? #
Writes are batched, heavy data goes to files, and cache sweeps are throttled.
Will the admin get slow with lots of data? #
Widgets load one by one from summaries; retention keeps raw data bounded.
Related articles #
- How the tracking script works
- Cache plugin compatibility
- Tracking not working checklist
- Contacting support
Numbers #
| Item | Size / behaviour |
|---|---|
| Main tracker | About 44 KB minified, less compressed, deferred |
| Consent script | About 15 KB minified |
| Recorder (Pro) | Record-only build about 68 KB, starts after load |
| Sending | Batches every few seconds (3 s default) |
More questions #
Should I exclude the trackers from my optimiser? #
Usually not needed – they are registered automatically. Add an exclusion only for optimisers not listed in Cache plugin compatibility.
Does Opti-Behavior load anything from external servers on my pages? #
No. Trackers are served by your own site.
What about the admin? #
Dashboard sections load one by one and can be folded; big sites stay usable.
