Basically, Breeze cache all JS and CSS files called activated theme and creates a cache of the theme in a separate path. The URL you have mentioned in the cache path of JS and CSS files.
The suggestion given by Google Insight is about to reduce unused CSS and JS files. You can handle it by reducing them as per your theme functionality.
Thread Starter
djeah
(@djeah)
@adeelkhan Thanks. I managed to remove a lot of unused ones using Asset Clean-up.
However, when I select to group the CSS, I get the unused CSS suggestion by PageSpeed Insights, but if I unselect the grouping in the setting, that error goes away!
The scenario which I understand that while you enable JS and CSS minification except Grouping than you did not get suggestion of unused CSS? while you enabled Grouping then you will get the suggestion
First, you have to clear your cache by using the “Purge All Cache” option in Breeze because it’s quite possible that while you remove your unused CSS but still content serves from the cache.
Another option is that could you please verify that is there any plugin used by the activated theme which used any CSS from the widget?
Thread Starter
djeah
(@djeah)
Hi @adeelkhan
CSS is resolved. It is only the JS part which is pending now. Every time I make a change on my website I make it a point to clear the cache from breeze and also from Cloudflare. I will update you on the JS part today.
Thread Starter
djeah
(@djeah)
Hi @adeelkhan
Not able to resolve the Javascript part of this. After every configuration change I am erasing both cloudflare and Breeze cache. When grouping and minification of JS is not enabled in breeze I do not get the ‘Remove unused JavaScript’ error in Pagespeed insights
While enabling Grouping of JS minification the entire JS code rendered from one file. In your scenario, the entire script is not used that’s the reason Page speed suggested that split JavaScript into essential code to render the page.
