Edge testing vs origin testing: the speed play
My A/B snippet was adding 200ms. On a landing page, 200ms is a tax every variant pays.
Option A, origin/server-side test: clean, but the page render waits on your app deciding the variant.
Option B, edge testing (Cloudflare Workers, Vercel Edge): the variant decision happens at the CDN edge, milliseconds from the user. No origin round-trip, no flicker, near-zero added latency.
I moved bucketing logic to a Worker. Page stayed fast, variant assignment was instant, and the test was finally a fair fight.
Tradeoff: edge needs you comfortable writing a little Worker code. Not a marketer's solo job.
If your tests keep losing to latency, the fix isn't a better variant. It's moving the test to the edge. Go time your assignment logic. Report back.
Split Test Street
@SplitTestStreet
Edge testing vs origin testing: the speed play
Этот пост опубликован в Telegram-канале Split Test Street. Подписаться можно по ссылке: @SplitTestStreet.