This message was deleted.
# contributing
w
f
Flickering is a problem with client side AB testing. There are a few strategies that you can take. One is to make the loading of GrowthBook a blocking call (not ideal). Another is to hide the button initially (or whole page), and show the button (or page) only after the variations load.
We feel that all “anti-flickering” techniques have their pros and cons. We built GrowthBook to be as fast as possible, so even by moving the SDK code higher up on the page rendering loop might be sufficient to stop the flickering.
a
regarding hiding the page, you can recreate what Google Optimize did with the flicker. Not ideal, but doable.
f
ya, we probably can - can you open a ticket for this?
👍 1
452 Views