Target user experience question - A/B test page loads control then reloads variant?

We are running a relatively simple A/B test on two versions of a page using AEM and Target - both pages exist on AEM, the variant is the child of the control. When it launched, our group noticed that the control page was loading for a second or two and then the variant would load. We were told by our testing group that this is the way Target works and cannot be changed.

Is this true? Does Target always load the control and then the variant? I am very new to Target, and very eager to learn more about it, but if the default behavior for an A/B test is to show the control long enough for content to load and then take it away from users, then perhaps this isn't the best tool for testing.

Thank you!