submenu

Hello @aurimasv

This is sadly not something that can be “easily fixed” because it is more related to how Litespeed’s algorithm processes CSS. We cannot affect this from our end.

With Blocksy, we already employ all the optimisation features that are available for the web, so processing its files once again with a caching plugin can have negative consequences.

You can read more about this phenomenon here – https://creativethemes.com/blocksy/docs/troubleshooting/the-case-of-over-optimising-your-website/

What I would recommend for you is to exclude Blocksy’s files from being processed by lite speed, by excluding /wp-content/themes/blocksy and /wp-content/plugins/blocksy-companion(-pro). This should give you more consistent results, while also keeping the optimisation turned on, since it’s already implemented at the code level.

Hope this clears things up!

Thanks.

Hello @aurimasv

Did you try excluding optimisation entirely for admin users?

Sadly, without seeing the browser console, I cannot comment much on what’s going on. Could you get back to me with a few more details on this one?

Thanks!

Hello @aurimasv

Well, these exclusions are not set up correctly, if you just copy pasted them. I would recommend checking out lite speed documentation for how to set up these exclusions correctly. I was just merely giving you the paths to know what to exclude. 🙂

Thanks.

You’re welcome, @aurimasv

Please let us know how it goes and if you need further assistance from our side.

Thanks!