We need solutions for those kind of problems, we have them an all bricks pages…even if we deelete the 20kb image…the next element will be take as pitfall…on desktop we have here 99 points…
There are a couple of old but still open/unanswered “LCP reports” – independent of Bricks – with swiper.js, the slider library we’re using for the slider and carousel, so I wouldn’t consider this a general Bricks bug.
I see two ways to improve the performance possibly:
deactivate the ‘Loop’ setting of the slider
change the slider element and use the nestable slider with properly sized real images instead of background images
on our page we dont have the slider element here…its an ordinary background image div…and even if we delete that whole element and have no background element here at all…the speed tester recognized just the next element in the HTML line…and says this is now the CLS problem…it must be something else in your case at least…
I’m not sure to which website you refer, but the site from your original report has a slider at the very top. Since I have no other information or links, unfortunately, I can’t say anything more about your issue
