Wordpress LScache Plugin: Divi theme & LSCache Optimisation Settings
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, Your plugin claims that its fully compatible with the Divi theme. However, I noticed that styling breaks, if I enable all of the most useful CSS/JS Optimisation Settings. Do you have a recommendation for Divi powered websites as to what is safe to enable and whats not? For example, I found out that I had to keep Lazy Load Iframes disabled, because core Divi modules would take ridiculous amount of time to load and would also often break styling (e.g. Blog module, post slider module etc) Regards, Alex Hi, Could you please provide report number ? Best regards, Hi @CacheCrawler, I dont have a report number. But you can replicate the problem by enabling JS Combine in LSCache Settings and then trying to open a saved Divi Library item. The builder will load forever. And there are errors in the console. For example: Uncaught SyntaxError: Unexpected end of input Regards, Alex Hi @CacheCrawler, I just tried something, since I noticed that combined JS file does, indeed, end abruptly (hence why Unexpected end of input message). So I increased Max Combined File Size to 3MB and now backend Divi Builder is loading fine in Divi Library. Why would that be happening? Seems like as LSCache is splitting combined JS into multiple files, its breaking the JS code, since it just cuts right in the middle of the code, thats very weird. Shouldnt it combine files up-to, but no more than XX setting in Max Combined File Size instead? And if new JS doesnt fit, it should push the it into the next file.. UPDATE: Apparently, it wasnt just the Max Combined File Size setting, which was causing the Divi Builder crashes. Setting Remove Comments to ON also breaks New Divi Builder. This is the console error message: Uncaught SyntaxError: Unexpected identifier Regards, Alex Hi, Yes ,sometimes if too many JS files to be combined , it will have a huge file may negatively impact the performance. Will set up and test it. So please confirm: remove comment ON -> breaks it Max combine size to 3 MB -> solves it if you do not combine JS , and only remove comment , does it break ? Best regards, Hi @CacheCrawler, Yes ,sometimes if too many JS files to be combined , it will have a huge file may negatively impact the performance. It didnt negatively impact the performance, it broke the JS scripts completely by splitting them right down the middle of the function, once the 1.2MB limit was reached. If the files were instead combined WHOLE, up to that set MB limit, then this wouldnt happen. Yeah, the combined file might not be exactly 1.2MB, but at least it wont have broken/cut-off JS functions in it. remove comment ON -> breaks it This breaks the code completely (if JS Minify is ON), regardless of the JS Combine setting. You will see the Uncaught SyntaxError: Unexpected identifier error. Max combine size to 3 MB -> solves it This solves the Uncaught SyntaxError: Unexpected end of input error. I would also advise anyone seeing this error, to actually increase the limit up to 4-5MB, because you need more space if you were to include jQuery in the mix. Regards, Alex Hi, Could you please submit a ticket here ? we will investigate it deeper Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference