Q: Delay in Variant Rendering During A/B Test
Before subscribing to your offer, we wanted to test your solution. However, we noticed an issue: the script loads slowly. Specifically, the original version of the page appears first, and then, about one second later, it switches to the test variant (for example, the default H1 is displayed and then replaced afterwards by the modified H1).
Could you let us know if this behavior is expected? Are there any recommendations to avoid this visual delay, or is it a known issue that will be fixed?
Ian_PageTest.AI
Sep 15, 2025A: Great question, what you’re seeing is the classic “flicker” (the control renders, then the variant replaces it). It’s normal if the testing script fires a moment after the initial paint (common with GTM defaults), but we can reduce it to near-invisible.
Here’s how to tighten it up:
1) Fire the snippet as early as possible
Direct install: Place the PageTest.AI script at the very top of <head>, before other third-party tags. Don’t add async/defer to our snippet.
If using Google Tag Manager:
Use Tag Type: Custom HTML, Trigger: Initialization – All Pages (or Consent Initialization if required).
Set Tag Sequencing so nothing delays it.
Avoid triggers like “DOM Ready” or “Window Loaded” for our tag.
Ultimately the script firing speed will be a factor of the overall site loading speed, the first paint of the site and the total number of scripts will play a part in this.
noicenetizenPLUSwould love to know it too
107764231855707643967Hello, thank you for your message. However, after completing the payment and testing your script in production, it directly conflicts with the reCAPTCHA scripts, which is problematic. I reached out to your support team, but I haven’t received any response for over 24 hours. I hope to get a prompt reply; otherwise, I’ll be forced to request a refund. Have a good day.