Search for articles…
The page stays blank for a few seconds
If your page stays white for a few seconds and then appears all at once, the anti-flicker script is doing its job but the engine isn’t arriving to reveal the page. The page only shows when the safety timeout runs out.
1. Why the page waits
The anti-flicker script hides the page as soon as it starts loading, and the engine reveals it the moment the visitor’s variant is applied. As a safety net, the page is revealed anyway after a fixed time: 3.5 seconds in the standard snippet, and 3 seconds by default in the WordPress plugin.
So a blank page that lasts about that long means the engine didn’t run in time. The most common cause is an optimisation plugin that holds JavaScript back until the visitor scrolls, clicks or moves the mouse.
2. Exclude the engine from delay settings
In your speed or caching plugin, find the setting that delays or defers JavaScript (often called “Delay JavaScript execution”, “load on user interaction” or similar) and exclude:
cdn.splitlab.io — where the engine loads from
mvt-engine-script and mvt-anti-flicker — the two scripts added by the Splitlab WordPress plugin
If you serve the engine from your own first-party domain, exclude that domain too. The WordPress plugin already opts out of WP Rocket, LiteSpeed Cache, Cloudflare Rocket Loader and Autoptimize, so this step is mainly for other optimisers.
3. Check the engine actually loads
Open the page, then your browser’s developer tools and the Network tab. Filter for engine.js. It should load from cdn.splitlab.io with a 200 status. If it’s missing, blocked or only appears after you interact with the page, the exclusion hasn’t taken effect yet.
Also check the script tag has a non-empty data-project-key. Without a project key the engine has nothing to serve.
4. Clear your caches
Purge your plugin’s page cache and any server or CDN cache, then reload in a private window. Old cached pages can keep the delayed version of the script for a while.
5. WordPress: the “Reveal anyway after” setting
In WordPress, go to Settings → Splitlab. Reveal anyway after controls the safety timeout and accepts 500 to 10000 ms. Lowering it shortens the wait while you fix the optimiser, but it doesn’t fix the cause: if the engine still arrives late, visitors may see the original page before the variant.
6. Still stuck?
Send us the page address and the name of your caching or optimisation plugin. Contact us or email team@splitlab.io.
Related articles
Still stuck?
Email team@splitlab.io or send us a message.
Contact us