All terms

CRO Glossary

Flicker Effect

A brief flash of the original page content before a client-side A/B test variant renders and replaces it.

The flicker effect (sometimes called the FOOC — flash of original content) happens when a testing tool changes a page after it has already started rendering. The visitor sees the control version for a split second, then the page visibly shifts to the variant, which can look like a glitch or feel jarring.

This matters because it undermines the integrity of the experiment as well as the user experience. If visitors notice the swap, it can bias behavior (they may distrust the page or simply be distracted), and it can also make the control look artificially better since the variant effectively had a delayed, worse first impression. On slower connections or heavier scripts, flicker gets worse, which means your test results can be confounded with page speed rather than the actual change you're testing.

The usual causes are client-side (JavaScript-based) testing tools that wait for the page to load before injecting changes. Common fixes include anti-flicker snippets that hide the page until the variant is ready, moving logic higher in the page load, or switching to server-side testing where the variant is decided before the HTML is sent to the browser.

For example, a pricing page test that swaps a hero image via JavaScript might flash the old image for 200-400ms before the new one appears — enough for analytics to record a slightly different bounce pattern between control and variant, muddying the read on which version actually performs better.

Related terms

See this in the wild

ABWatcher watches how top teams apply flicker effect.

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