tabasco86 on "[Plugin: Autoptimize] 376 files, totalling 414891 Kbytes in Cache"

ok, so I had a quick look, the reason is you have significant differences in the CSS being loaded between different pages (I compared your home, /loja/ and /ideias-para-decorar/).

gravity forms, for example, is loaded on /loja/ (a.o. the contact widget), but is not loaded on your homepage or on /ideias-para-decorar/, which means that due to the GF CSS being added on /loja/, the CSS from /ideias-para-decorar/ cannot be reused.

similarly, /loja/ and /ideias-para-decorar/ have CSS with "yoStar" in the selector (I guess for product star ratings), which is not on the homepage.

the result; 3 different CSS-files for those 3 pages. and as you have _a lot_ of CSS, that results in a significant amount of disk space used AND in the fact that the CSS needs to get re-downloaded when going from home to /loja/ or /ideias-para-decorar/.

a solution for this could be to switch to a whitelist for CSS, where (using the API) you tell AO what can be autoptimized (instead of the blacklist-approach on the settings-screen), e.g.;

add_filter("autoptimize_filter_css_whitelist","test_css_whitelist");
function test_css_whitelist() { retu "style.css, dashicons.min.css, edd.min.css";
}

if you build that whitelist based on only all major shared CSS (starting with e.g. your theme's CSS but also the CSS of plugins that are active on the majority of pages/ posts/ products), you should be able to ensure a better re-use of cached CSS, resulting in fewer files and less disk-space used (while, on the other hand, you will have CSS this will not be optimized any longer, as it is not on the whitelist).

hope this helps :)

frank

- - , .
.