unused css = the same as render blocking one

for the render-blocking part; look into “inline & defer CSS”, more info in the AO FAQ.

for “unused CSS”; it is being reported as being Autoptimize’s, but AO merely aggregates all the CSS provided by your theme & plugins, so if you (really) want to tackle “remove unused CSS” then you should look into your theme & plugins (you might be able to get some improvement using e.g. “plugin organizer” to only allow plugins to work on specific pages). Moreover the unused CSS will likely be different for different pages (or parts of your site), so that would lead to different autoptimized CSS-files being loaded on different pages.

hope this clarifies,
frank

hello,
i spoke to jevelin theme support, and they said they are not aware of double css that they inject,

do you have any idea how i can find the cause for this unused css:
saveatrain.com/blog/wp-content/cache/autoptimize/css/autoptimize_fbff5765c3c2319fe91a62c678925152.css
comes from: https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.saveatrain.com%2Fblog%2Ffamous-film-spots-europe%2F&tab=desktop

i am already using inline and defer

this is what Chrome Developer Tools “coverage” has to say about unused CSS on the unoptimized page:

(direct link for higher res. enjoyment; https://i.imgur.com/sobsA3F.png)

may i ask what am i missing here, since i don’t see here duplicates, while you told me the unusued css comment by autoptimize is because the theme is creating a duplicate ??

thanks for trying to help

The pagespeed recommendation is not about duplicate files, but parts of CSS loaded that are not used to render the page. That is what you can see in the screenshot I made, where for example the main theme CSS-file has 90% code that is not used on your homepage. This is not something that can easily be changed and is not uncommon for theme (and plugin) CSS-files.

so basically forget about this issue right?

well, you *could* ask the theme devs to split the big CSS-files up in smaller ones and have those only added when needed, which would result in less unused CSS, but that is not a small task and it is my feeling that GPSI grossly overestimates the gains that can be made when doing so, so I don’t feel this is worth it really …

thank you for this,
do you see anything else i need to allow on autoptimize, or i reached the peak of optimization with your tool? ??
hope you had some kind of Christmas holiday.

Well, adding display:swap to the CSS that loads the locally hosted fonts could help improve the First Meaningful Paint (bring it closerto First Contentfull Paint), but those are changes that will likely need to be done at a theme or plugin level (which ever sets those fonts).