When your webpage is loading, it can sometimes occur that the original page displays for a split second instead of the variation. This twinkling is called flicker effect or flickering.
Why this flickering?
This flickering happens because of the time needed for the JavaScript engine to process the page.
It is one of the very few disadvantages of having a 100% JavaScript engine on which are based A/B testing solutions. Indeed, the elements will be changed according to the order indicated in the JavaScript code created by the A/B testing tool.
Consequently, if Kameleoon script loads after the webpage, the variations will also load last, creating this flickering.
How to avoid it?
Kameleoon’s engine is maximized to limit the flicker effect. Therefore, you are unlikely to encounter this inconvenience during your A/B experiments.
Besides, we highly recommend to integrate Kameleoon JavaScript code as high as you can on the HTML page, ideally right after the <head> element to make sure Kameleoon loads first.
