Browser: Chrome 110
OS: macOS / Windows / Linux / etc.
URL: Link to a page that illustrates this issue
Video: Short screen recording that illustrates this issue (free tool: jam.dev)
[Please describe this bug in as much detail as possible so we can replicate & debug this bug]
Please see here: Jam
Builder loading way slower initially now?
Did you disable 3rd Party Bricks Plugin Enhancements and ACSS and other stuff to see if it is conflicting or not?
It loads fast for me.
If you have so many 3rd party plugins that are not tested with the beta, you kind of need to see if there is a conflict there.
Can you run the test without any Bricks add-ons enabled and share the total builder loading times with 1.9.8 and 1-9.9-beta enabled, respectively? Thank you.
I did disable, but I have lots of elements in there from Frames and using Bricksforge GSAP, so it makes it borderline impossible for this install to pinpoint it sadly.
I would say it was maybe 3 seconds slower - but then the olde Bricks would ‘then’ load the elements in, whereas this one kinda does it at the same time it loads the screen?
Feel free to email us some temporary admin login details for your site so we can try to replicate the issue. Please also include the exact URL where the slower load time occurs, plus a link to this forum post as a reference. Thank you.
Thanks Thomas. I’ll keep an eye on it, as since I cleared all my browser cache and used Safari to double test it, on my work Mac, it does seem to be pretty much the same as previous now… Ironically!
I wonder if it was my home Mac combined with some initial load delay from moving versions. I’ve submitted a few other bugs though related to content delays / updates in the builder, so hopefully that helps get to the bottom of those.
I’ve updated the post title to “NO BUG”. If anyone can share an A-B test where 1.9.9 loads slower than 1.9.8, please let us know here.
@robp Possibly. Running any machine for a prolonged time can clog up the RAM, causing a noticeable performance degradation.
Bst to restart the machine before running a performance benchmark test to out rule or at least minimize any unwanted side effects from skewing those tests.
RE the login details, I sent some over to Charaf which Stefan used earlier to check another bug I was seeing. It’s mostly trying to edit any of the work pages, especially the longer ones (fostering for example). Thanks