Hello there @themightydvir,
hope you’re doing well today! 🙂
In short, in order to remove render-blocking resources, you should remove any assets (CSS and JS files) that’s getting loaded in the page <head> and move it to <footer>, for all elements that’s above the fold (above the initial screen that’s getting loaded, before you start scrolling). So the initial screen will load only what’s needed, making it super fast.
Please keep in mind that this isn’t 100% possible most of the times, as there could be some theme or plugin that it would require an asset to be in the head element, so everything works well. So this is a trial&error procedure and better to be performed in a staging environment when the actual development is finished.
Back to HummingBird, the Asset Optimization module provides an “advanced mode” that you can use to move assets to the footer (or “defer” in case of JS). You can find the documentation about this module here:
https://premium.wpmudev.org/docs/wpmu-dev-plugins/hummingbird/#chapter-4
And there’s also an article in our blog that around that specific case and HummingBird:
https://premium.wpmudev.org/blog/eliminate-render-blocking-issues-hummingbird/
Hope that was some help!
Warm regards,
Dimitris
Hello @themightydvir
It’s been a while since we’ve heard back from you so I’m marking this topic as resolved. Feel free to post back any updates and we can re-open it and carry on troubleshooting. 🙂
Thank you,
Dimitris
