@dreamzspl the files that are stored in the caching directory of Asset CleanUp, which by default is /wp-content/cache/asset-cleanup/. Google PageSpeed Insights is reporting anything that is unused and render-blocking, no matter where it resides. If you make a test and append to your URL /?wpacu_no_load which will not trigger any Asset CleanUp functions, you will still notice the same thing, the only difference being that the files are loading from their original location.
Even though Asset CleanUp minified/altered the CSS/JS file, it’s still render-blocking and contains unused CSS. It just loads from a different location because Asset CleanUp, after it minifies the file, has to store its contents somewhere for faster loading.
There’s a special post written especially to clarify this here: https://www.assetcleanup.com/docs/can-the-plugin-load-render-blocking-css/
Please go through it and let me know if still need any assistance!
Hi @gabelivan , so you mean that the original CSS / JS files are already render-blocking in the first place? Therefore Asset Cleanup does not interfere in the render-blocking nature of these files?
Is there a way to use Asset Cleanup to identify the original unused CSS / JS files and unload them?
And wonder if there is a possibility for Asset Cleanup to have the function to control render-blocking resources in future? 🙂
Thank you!
so you mean that the original CSS / JS files are already render-blocking in the first place? Therefore Asset Cleanup does not interfere in the render-blocking nature of these files?
Of course, they are render-blocking in the first place as it would be against the purpose of the plugin to just make them block the rendering of the page and have a lower score in Google PageSpeed Insights. It’s just a matter of the disk location from where they are loaded as Asset CleanUp has to alter them and serve them from a different location. In fact, I’m considering changing the name of the caching directory to something else as too many people think that the plugin is causing all the unused CSS and render-blocking warnings which is non-sense.
Is there a way to use Asset Cleanup to identify the original unused CSS / JS files and unload them?
Asset CleanUp can help you unload whole CSS/JS files (which are identified in the “CSS & JS Manager” area), but you have to decide which ones are not needed on certain pages. There are also tools such as Coverage which could help you identify unused CSS. You can read about it here: https://www.assetcleanup.com/docs/how-to-check-if-gutenberg-blocks-css-file-is-needed-or-not/
And wonder if there is a possibility for Asset Cleanup to have the function to control render-blocking resources in the future?
To make a JS file render-blocking you have to “defer” it and make a CSS file load in an asynchronous way (non-render blocking), you can have to preload it in an asynchronous way. These features are available in the Pro version of Asset CleanUp. However, if you use a plugin such as WP Rocket you can also remove render-blocking resources. Here’s a post about it here: https://www.assetcleanup.com/docs/eliminate-render-blocking-resources/
There will be more documentation about these render-blocking resources so that everyone would understand how they work and one of the features that eliminates completely any render-blocking CSS is “Critical CSS” which is under development. I’m looking forward to having it released. It will offer granular control over the pages where it will be activated, like enabling it just for the homepage and a few key pages with the option to edit it so it could be polished as one wishes.
