Clean installation of WP and Bricks - no plugins, the builder works quickly and efficiently even with a large number of elements on the page.
After installing ACSS and Frames (and thus loading a large number of classes) and building a layout based on Frames, the builder starts to stutter, section copying is severely lagged.
The first page made on bricks alone (without using classes) still works fast and copying of sections is done practically immediately.
Sorry for the long video (10m), at the beginning it shows that it works quickly without stutters, and the biggest lags are visible at the end of the video with ACSS and Frame plugins installed and on a website built with Frames layouts.
Thank you for creating this separate thread and for the video you provided. This is a work in progress, and we appreciate your detailed feedback as it helps us identify and address specific issues. So far, these are the specific instances of lag we’ve noticed on sites with a large number of global classes, which we are actively working to improve:
The global class manager is slow to open.
Clicking on a class in the global class manager is slow to open the editor (third column).
Clicking on the classes dropdown in the element settings can be slow to open the dropdown.
Removing classes from an element.
Additionally, performing the operations mentioned above for a while could freeze the whole builder and cause lag elsewhere for some time (e.g., removing a class then attempting to duplicate or rename an element immediately). In this case, the lag is attributed to removing the class.
For that reason, please share very specific steps and preferably a screen recording if there are any other particular instances that could cause lag that we might have missed.
I can confirm that the lag you describe also happens to me sometimes, but not always. Now, for example, when I wanted to record them, they didn’t appear, but they definitely happen to me. If I have any further information, I will send it. Thanks very much and I look forward to solving the problem.
Any updates on this front? The lag is killing me and that is apparent in 3 separate sites right now. As long as the structure and the number of elements with custom global classes piles up the editor because a real pain to use…I am really lost here and don’t know what do. We have the best WP builder ever made and I can’t be productive because of this issue…It is really slow to work with.
@charaf This is with the 1.9.8 Beta and renaming elements is unusable, duplicating or even expanding the structure panel is dog slow…
I just made a copy of this specific instance (staging) and disabled ACSS and Advanced Themer and although the lag is less it is still there…All it takes to bring the Editor to a crawl is duplicating the structure of this page (i.e. adding a lot of elements). With ACSS disabled there are 610 classes on the database.
If I start adding custom classes (needed!) and then custom JS code it will end up the same crawl nightmare…the problem is a combination of the number of elements and classes.
I’m having this issue as well with a new build using ACSS. Building with Local, but it was also occurring on the ACSS 3.0 sandbox site.
All the issues listed above are prevalent, and when a page has more than a couple sections on it, there’s a ~0.7s delay when clicking on any element.
@Jargon@sunny@batorbator Please update your Bricks installation to version 1.9.8, as it includes several performance improvements that could potentially address some of the issues you’re experiencing. After updating, please test the performance again (except for the lag observed after duplicating an element, which is still a work in progress).
To be more specific we were able to reliably replicate and improve these issues in our latest release that were mentioned in this forum thread:
Class manager: Opening the manager should be much snappier
Class manager: Snappier selecting of class(es) in the manager
Element class dropdown: Should open snappier
Element: Select/add/remove class on an element should be snappier
If you’re still encountering performance issues, we recommend temporarily disabling all plugins to check if the problem persists. This step is important as it helps isolate the issue. If the lag decreases significantly without plugins, then please try re-enabling ACSS or any other CSS framework plugin alone, since it contains a large number of classes.
@sunny, regarding the delay of about 0.7 seconds when clicking on any element, we have been able to replicate this issue in cases where new elements do not have any settings applied. However, as you’ve noted that this occurs with every element, it would be really helpful if you could provide a screen recording showcasing these specific actions. Please send this recording, along with access to a staging environment where we can replicate the issue if possible, to our support at help@bricksbuilder.io.
We ask everyone experiencing other issues to share very specific steps, and if possible, a screen recording of any particular instances that could cause lag as mentioned here:
@jargon, as mentioned in my previous email, if you could replicate this behavior on a page using only Bricks native elements, it would be helpful. While we understand the necessity or desire to use third-party tools, please remember that managing and optimizing those tools falls under the responsibility of their respective developers.
We appreciate your patience and cooperation as we work through these issues.
Hi @batorbator, we have a potential fix for the duplication lag that we’d like to test on different setups. If possible please share temporary admin access to a staging environment to help@bricksbuilder.io with a link to this forum thread so I can upload the fix for you to test
Edit: @Jargon I have uploaded the duplication fix to your staging site as well. Please disable all plugins whilst testing (except ACSS).
As I’ve mentioned earlier the duplication lag is a separate issue that is still a work-in-progress:
I have uploaded the potential fix/improvement to your staging site. Could you please try again and let me know if you can see improvements on your end too?
Yes! there is a big improvement, duplication is done practically immediately. There is maybe a small delay of 1-2 seconds, but I can work like that. However, there is still some delay when deleting sections/elements, as I show in the video: https://jam.dev/c/456b71dc-57b2-4d8b-892c-a2682c304db3
It’s great that you managed to deal with it, thanks a lot.
If I want to make this change on my other installations, can I do it myself or do I have to wait for the next release of bricks?
Regarding the element deletion lag, I can slightly replicate it on your site (it’s not instant but doesn’t take longer than 1s on my end), but in your recording, it’s much more significant on your end. Can you please try it in an incognito window perhaps (to rule out extensions interference)?
I am really glad that I can finally see several improvements but I need to test more since there is still some lag in renaming elements but duplication is much better. Today I was “racing” to send a demo to a client and after updating to 1.9.8 things were certainly better with the structure panel (from unusable to “can work”).
I will test 1.9.8 on another staging site too (many more elements on a page there) that was really slow and also share access. I am sorry for being slow the last few days but deadlines breathing down my neck!
In any case, thanks for working on all these performance improvements!
Thank you for your continued patience and feedback
We’re happy to share that we have identified the bottleneck causing performance issues in the builder under certain conditions. We have implemented a fix, which has shown promising results in our internal tests.
I will be reaching out to some users to test these new improvements.
I’ve having huge issues with builder lag, 4/5 seconds with almost every command. Using a few Bricks plugins but I’ve taken them off and it seems to make little difference.
Is there anywhere I can share a login with Bricks support please and somebody could shed any light on why it’s so painfully slow? I can stab a guess that some of the pages are long/huge and have dynamic content in, which is maybe I suspect a cause.
