- URL: https://wordpress-1225960-5211874.cloudwaysapps.com
- Video: Homepage | Malvern Garden Buildings - 24 January 2025 | Loom
We’re experiencing serious builder lag on multiple client sites, when the page is complex, with multiple query looped elements on the page.
We’re using Frames.io and have sections containing splide sliders that are query looped. If i remove the query looped sections, the builder lag disappears.
Things I’ve changed/tried:
- I changed the queries for a few of the sliders in use to query for the object ID only instead of the image URL through ACF, as attachment_url_to_postid can be resource intensive.
- I’ve cleaned up the functions.php code and my own plugin code thinking it could be something here, but with no change. I completely cleared the functions file of any custom code at one point, and it still happens.
- I’ve updated to bricks 1.12.1 and converted necessary templates to components
I’ve been in touch with the Digital Gravy team, and they have concluded that it’s the builder rather than frames specifically that is responsible:
This is a Bricks issue, is not ACSS even Frames. Only occurs in the builder context when you have a lot of sliders with query loops. If you use 5 sliders without loop the lag is minimal, but when you use a loop just crash the builder. In frontend it causes some lazy load but doesn’t crash the entire site.