All terms

CRO Glossary

Flicker Test

A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.

A flicker test is a practical check teams run to see whether the original (control) content momentarily appears on screen before a client-side experiment swaps in a variant. This flash of unstyled or original content happens because the page has to load, then JavaScript has to detect the user's assigned variant and rewrite the DOM, creating a visible delay even if it's just milliseconds.

This matters because flicker isn't just a cosmetic annoyance — it can bias results. Users who notice the page "jump" may behave differently than those who don't, and the flicker itself can suppress clicks or trigger distrust, especially in product or pricing pages. It's a classic confound that threatens the validity of a test without ever showing up in the metrics directly.

To run a flicker test, practitioners typically record screen captures at normal and slowed-down speeds, or use browser dev tools to throttle network/CPU, watching for a visible flash of the control before the variant appears. Teams also check anti-flicker snippets (small scripts that hide the body until the experiment engine decides which variant to show) to make sure they're firing correctly and not themselves adding noticeable delay.

For example, a team testing a new homepage hero might discover during a flicker test that on slow mobile connections, users see the old hero image for half a second before the new one loads — long enough to let them scroll past it and never register the change.

Related terms

See this in the wild

ABWatcher watches how top teams apply flicker test.

Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.