Well, render-blocking resources _can_ be improved with AO, but it’s a matter of configuration;
* for CSS look into “inline & defer CSS”, see the AO FAQ for more info.
* for JS make sure “force JS in head” is NOT checked and either “aggregate JS” or “do not aggregate but defer” are checked
always happy to help in the support forum if you need further assistance! 🙂
frank
Thread Starter
Pat
(@patrickhaond)
Thanks for the answer.
I followed your advices for JS matter.
Same thing with CSS…
When I test with Lighthouse, autoptimze css file is even the file where I could potentially save 2,100 ms !
The unused CSS is being reported as being Autoptimize’s, but AO merely aggregates and minifies all the CSS provided by your theme & plugins and does not know which CSS is used or not used and hance cannot remove anything.
There however is a new premium service that can remove unused CSS that could help. For more info see the Rapidload entry on Autoptimize’s “Optimize More” tab.
hope this helps,
frank
Thread Starter
Pat
(@patrickhaond)
Thank you for your answer.
I can understand AO agregates all files, so quite logical, but in the end it didn’t save anything.
Ok for the premium service, but difficult to accept to pay while the free version didn’t help at all.
Thanks for your time.
in the end the aggregated file will be smaller then the sum of all individual files as the CSS is minified, but minification is only removing comments & spaces & newlines, not removing selectors/ styles, which is why “minify CSS” and “remove unused CSS” are 2 different recommendations 🙂
