@akashkms01 @gooma2 Indeed, Google PageSpeed introduced some changes such as “Remove unused JavaScript” which is even more difficult to remove than the CSS as Coverage DevTools which is often used to determine unused bytes is less accurate (due to the nature of the JS code, not the tools fault I would say) to detect which JS files are needed and which not.
@akashkms01 on your website, there are still asserts that are likely not needed and can be unloaded, including:
– https://thefreegyaan.com/wp-includes/css/dist/block-library/style.min.css
– https://thefreegyaan.com/wp-content/plugins/pwa-for-wp/assets/css/pwaforwp-main.min.css
– https://thefreegyaan.com/wp-content/plugins/easy-table-of-contents/vendor/icomoon/style.min.css
– https://thefreegyaan.com/wp-content/plugins/easy-table-of-contents/assets/css/screen.min.css
– https://thefreegyaan.com/wp-includes/js/wp-embed.min.js
Currently, Asset CleanUp supports unloading whole CSS/JS files. You can’t strip partial code from specific files. There are ways to unload a CSS/JS file and load an alternative (lighter) version of that file with considerably less code, thus, reducing the total page size and having it load faster by the browser. Based on my experience, this is worth implementing for pages with high traffic. I’ve noticed CSS code that was unused in 90% of the cases and it was worth going through it (sometimes you spend hours testing and making sure the page looks exactly the same) in order to reduce hundreds of KB and have a faster loading page.
I’m considering providing more tutorials/documentation about removing unused CSS/JS as it’s one of the most popular topics out there, along with reducing render-blocking resources.
@gooma2 I’m having the same issue also and it’s showing for cache/asset cleanup files. – the reason it’s making reference to Asset CleanUp is that you have minified/combined or enabled an option that would alter the original file and has to store the optimized version in the cache.
Even if you weren’t using Asset CleanUp, the original file would still be reported as render-blocking or having unused code. So, Asset CleanUp did make changes to that file (e.g. it minified it), but for Google PageSpeed, it still has unused code there. I hope it makes sense!
In fact, there were quite a few people that mentioned this and thought that Asset CleanUp is adding render-blocking resources to pages which is completely false, it will never do that as it’s against the purpose of the plugin. I’ll make sure the documentation has a dedicated post about this clarifying this in detail so there will be no doubt about how this works.
