Hi everyone, are there any precautions GrowthBook SDKs take to avoid flickering from dom manipulations of Visual Editor experiments?

Hi Atakan, Thank you for writing in. GrowthBook takes several precautions to avoid flickering from DOM manipulations of Visual Editor experiments: 1. ​*Fast Loading*​: GrowthBook is built to be as fast as possible. This means that by moving the SDK code higher up on the page rendering loop, it might be sufficient to stop the flickering. 2. ​*Inline Experiments*​: You can reduce flickering by using inline experiments. This involves loading the feature payload inline, which can make sure GrowthBook is not waiting on other services for the hashing attribute. 3. ​*Server-Side A/B Tests*​: Another way to avoid flickering is by using server-side A/B tests. This can be a good alternative if loading the SDK in the head does not sufficiently prevent flicking. 4. ​*Anti-Flickering Scripts*​: If necessary, you can also use an anti-flickering script. These scripts hide the page while the content is loading, and reveal the page after the experiment loaded. 5. ​*Disabling Visual Experiments*​: Visual Editor experiments are enabled by default, but can be disabled with various GrowthBook constructor settings. If you set ​`disableVisualExperiments`​ to true, all visual editor experiments will be skipped. Remember, each of these "anti-flickering" techniques has its pros and cons. It's important to choose the one that best fits your specific use case. Hope this helps :)

Also consider using our Edge SDKs for flicker-less visual testing!