Small over the wire
The snippet is around 50 KB of source and arrives at the browser as roughly 15 KB with Brotli or gzip.
Performance
A small snippet from your own domain. Your page stays fast.
Delivery
Size, origin, cache, and the moment the variation takes effect.
The snippet is around 50 KB of source and arrives at the browser as roughly 15 KB with Brotli or gzip.
Served with max-age=300 and stale-while-revalidate: later pages do not fetch it again, and a change still reaches everyone within minutes.
Through a subdomain of your own domain the request looks like your own website to browsers and blockers, fewer gaps in measurement.
The anti-flicker option pre-connects and hides the area for at most one second, after that the content is shown regardless.
Variations that get by with CSS take effect before the first render. That is the safest route to an invisible test.
The SDK follows pushState and back/forward, undoes variations that no longer match, and waits for the element that signals the view is ready.
Anti-flicker
Hiding the page until the tool answers risks a white page. So abdriven hides it for one second at most.
Honestly measured
Snippet sizes can be compared so that everybody wins. So here is the basis: what counts is what goes over the wire, not the uncompressed source.
FAQ
No, the snippet does not block rendering. Just make sure a variation does not shift content at the top of the page.
Not necessarily. abdriven delivers compressed from your server. For worldwide delivery, put your CDN in front of it.
Technically yes. For speed, installing it directly in the head is better, because the tag manager has to load first, and that is exactly where flicker comes from.
Product