Title: Mobile render-blocking resources
Last modified: March 1, 2021

---

# Mobile render-blocking resources

 *  Resolved [carnets2routards](https://wordpress.org/support/users/carnets2routards/)
 * (@carnets2routards)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/mobile-render-blocking-resources/)
 * Hi there,
 * I read some topics about the becoming famous “Eliminate render-blocking resources”
   [here](https://wordpress.org/support/topic/eliminate-render-blocking-resources-19/)
   and [there](https://wordpress.org/support/topic/render-blocking-asset-optimization-not-helping/).
 * I’ve got a good score on desktop (97 on PageSpeed but I would like to improve
   the mobile one (it’s hard to know the perf score exactly, I just ran Lighthouse
   plugin on FF, then on Chrome then the PageSpeed website, and I’ve got three different
   results: 66, 84 and 69 >< )
 * The longest source to load is a hummingbird assets (css) and the heaviest one
   also (js).
    Asset Optimization says 6 203,0KB > 5 829,0KB (6%), I’m on Automatic
   Speedy.
 * Any help, advice or other on the subject will be more than welcome. Thanks in
   advance!
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fmobile-render-blocking-resources%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Support [Laura – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support8/)
 * (@wpmudev-support8)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/mobile-render-blocking-resources/#post-14117505)
 * Hi [@carnets2routards](https://wordpress.org/support/users/carnets2routards/)
 * I hope you’re well today!
 * I’ve visited the site in question and checked and those “Hummingbird assets” 
   that you mentioned are not really assets that “belong to Hummingbird plugin” 
   but are combined JS/CSS files created by Hummingbird Asset Optimization out of
   other CSS/JS files that your site normally loads.
 * To give you a better idea on what’s happening, let me give an example:
 * – let’s say that Hummingbird Asset Optimization is disabled on site
    – site loads
   3 JS files (5, 10 and 15kb in size) and 2 CSS files (15 and 35kb in size)
 * – that makes together total of 5 assets, JS being 30kb and CSS 50kb in total
 * – now you run Hummingbird’s Asset Optimization
 * – it compresses (minification) these files so JS in total becomes 25Kb and CSS
   40kb
    – and it combines them so instead of loading 3 JS files and 2 CSS files
   it loads no just one JS file and one CSS file.
 * Naturally, they might appear quite big and the more assets are combined together,
   the bigger these files are. But it’s still less files and they are compressed
   in comparison to no Asset Optimization.
 * However, to deal with render-blocking resources, you would want to go a step 
   further with this. Automatic Asset Optimization usually does a good job and I
   think in case of your site it preforms really well but it only compresses and
   combines files. It doesn’t change the way they are loaded.
 * So if you want to try to optimize it even more, you would want to
 * – switch Asset Optimization to “Manual” mode (make sure to use “Apply Configurations”
   while switching)
 * – you’ll see a set of buttons next to each listed file; first two already enabled
   for most of them (these are “compress” and “combine”) and then next three disabled
 * – the last one is to exclude file from loading at all so I’d ignore it but the
   remaining two are “inline” and “move to footer” for CSS and “move to footer” 
   and “load after page is loaded for JS.
 * – you would want to “experiment” a bit with this buttons to get as many “move
   to footer” (for CSS and JS) and “load after page is loaded” (for JS) enabled 
   as possible without breaking the site.
 * Note please: different sites may react in different ways to these settings so
   it’s better to set these options “few at the times” rather than all at once while
   checking the site every few changes made.
 * But this would let you eliminate as many “render blocking resources” as possible
   in this specific setup.
 * Best regards,
    Adam
 *  Thread Starter [carnets2routards](https://wordpress.org/support/users/carnets2routards/)
 * (@carnets2routards)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/mobile-render-blocking-resources/#post-14120613)
 * Wow, that’s what I call a support answer! Thank you so much for your time, it’s
   really clear. I’ll try the manual settings few at a time this week and come back
   to you if I see any changes.
 * Thank again for your help [@wpmudev-support8](https://wordpress.org/support/users/wpmudev-support8/)!
   
   Best regards, Claire
 *  Thread Starter [carnets2routards](https://wordpress.org/support/users/carnets2routards/)
 * (@carnets2routards)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/mobile-render-blocking-resources/#post-14122988)
 * Hi [@wpmudev-support8](https://wordpress.org/support/users/wpmudev-support8/),
 * I got a question, while I try to defer CSS and JS files, should I check every
   pages of the website at each change?
 * Because for example if I move the contact form CSS to the footer, it might work
   OK on the index but how it will perform if I go directly to the contact page?
 * Thanks again for your advice!
 *  Plugin Support [Imran – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support9/)
 * (@wpmudev-support9)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/mobile-render-blocking-resources/#post-14134160)
 * Hi [@carnets2routards](https://wordpress.org/support/users/carnets2routards/),
 * That would be correct. To ensure the assets being deferred are not causing issues
   on the contact page. Asset Optimization will detect all assets on site and each
   page will make request to certain assets per their need(depending on setup)
 * Let us know if you have any additional questions.
 * Best,
    Jonathan S
 *  Plugin Support [Nithin – WPMU DEV Support](https://wordpress.org/support/users/wpmudevsupport11/)
 * (@wpmudevsupport11)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/mobile-render-blocking-resources/#post-14206573)
 * Hi [@carnets2routards](https://wordpress.org/support/users/carnets2routards/),
 * We haven’t heard from you in a while, I’ll mark this thread as resolved now. 
   Please feel free to re-open the thread if you need further assistance.
 * Best Regards
    Nithin

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Mobile render-blocking resources’ is closed to new replies.

 * ![](https://ps.w.org/hummingbird-performance/assets/icon-256x256.gif?rev=2633221)
 * [Hummingbird Performance - Cache & Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN](https://wordpress.org/plugins/hummingbird-performance/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/hummingbird-performance/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/hummingbird-performance/)
 * [Active Topics](https://wordpress.org/support/plugin/hummingbird-performance/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/hummingbird-performance/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/hummingbird-performance/reviews/)

## Tags

 * [mobile](https://wordpress.org/support/topic-tag/mobile/)
 * [performance](https://wordpress.org/support/topic-tag/performance/)
 * [speed](https://wordpress.org/support/topic-tag/speed/)

 * 5 replies
 * 4 participants
 * Last reply from: [Nithin – WPMU DEV Support](https://wordpress.org/support/users/wpmudevsupport11/)
 * Last activity: [5 years, 3 months ago](https://wordpress.org/support/topic/mobile-render-blocking-resources/#post-14206573)
 * Status: resolved