Bricksforge Causing 4-5 Second White Screen Delay After Latest Bricks Update

After updating to the latest version of Bricks, my site displays a white/blank screen for 4-5 seconds on every page load before content appears. If I scroll on the page it loads. I’ve tested thoroughly and the issue only happens when Bricksforge is activated. When I deactivate it, pages load instantly with no delay. All other troubleshooting (clearing caches, checking errors, plugin conflicts) points to Bricksforge’s initialization being the culprit.

Is there a known compatibility issue between the latest Bricksforge version and the new Bricks update? Has anyone else experienced this? Any suggestions on how to resolve it?

Let me know if you need any specifics. Thank you!

Hi @nsmith,

thanks for the detailed report — and sorry for the trouble! What you’re describing sounds very much like Bricksforge’s FOUC prevention rather than a crash or a conflict.

Here’s what happens: if the Animation Panel has at least one enabled timeline (or a GSAP-based event action), Bricksforge adds a small style to the page head that hides the page body until the browser’s load event fires. The purpose is to prevent animated elements from flashing their end state before the animations initialize. The side effect: if the load event on your site fires late (large images, videos, third-party scripts, etc.), the page stays blank until then — which would explain the 4-5 seconds you’re seeing. It’s also possible that the latest Bricks update changed how assets load on your site, which made the gap noticeably longer than before.

To disable this behavior, add the following line to your wp-config.php:

define('BRICKSFORGE_DISABLE_FOUC_PREVENTION', true);

With that constant in place, the page paints immediately. The trade-off is that elements animated with “from”/“fromTo” animations may briefly flash their final state on page load before the animation kicks in.

Also worth doing independently of this: since the delay equals the time until your page’s load event, checking what delays it (large media files, external scripts) will improve things overall.

On our side, this mechanism has already been reworked for the next major version — instead of hiding the whole body until load, only the actually animated elements are hidden, and only until the animation runtime has applied their initial states.

Could you let me know if the constant resolves it for you? If not, please share your Bricks and Bricksforge versions and any errors from the browser console — then we’ll dig deeper.

Best,
Daniele

Thank you for your response. I’ll try this and see if fixes the issue. Will report back as soon as I can!

1 Like

This looks to have fixed the issue. Thank you so much!