Render Blocking

Hey, last time I used this product someone configured for amazing results. This time I have tried to get help, but have kind of been told support does not help. I have spent more than 10 hours trying to use product.
Google Page Speed shows WPMU files render blocking
URL
Size (KB)
Potential Savings (ms)
/?action=…(lakesidemethodistchurch.org)
3 KB
330 ms
/?action=…(lakesidemethodistchurch.org)
3 KB
630 ms
/lakesidemethodistchurch.org/3f87d5db-77c5-4a10-8807-8a45af….css(hb.wpmucdn.com)
0 KB
780 ms
/lakesidemethodistchurch.org/99e622e3-4496-4e82-8abd-693c50….css(hb.wpmucdn.com)
1 KB
780 ms
/lakesidemethodistchurch.org/1aa4e63c-e30d-45b8-b7e9-f2aacf….css(hb.wpmucdn.com)
33 KB
1,680 ms
/lakesidemethodistchurch.org/965d8011-f4c8-4d59-ae9e-72a327….css(hb.wpmucdn.com)
61 KB
2,130 ms
/lakesidemethodistchurch.org/9d09747d-98ae-4c8f-b9c5-a0f719….css(hb.wpmucdn.com)
1 KB
780 ms
/lakesidemethodistchurch.org/3c94b757-a0a7-4bac-bd90-6a105f….css(hb.wpmucdn.com)
1 KB
780 ms
/lakesidemethodistchurch.org/d52f2a77-ca20-45c8-8322-9337e7….css(hb.wpmucdn.com)
1 KB
780 ms
/lakesidemethodistchurch.org/aff11471-ff29-4540-bca6-2c9a44….css(hb.wpmucdn.com)
1 KB
780 ms
/lakesidemethodistchurch.org/100aa118-d28e-419f-976e-667…ec.css(hb.wpmucdn.com)
0 KB
480 ms
/lakesidemethodistchurch.org/45d38477-8992-4690-9eac-16e1b4….css(hb.wpmucdn.com)
1 KB
480 ms
/lakesidemethodistchurch.org/bcccb331-0dd3-4aa6-bfa2-51f166….css(hb.wpmucdn.com)
1 KB
480 ms
/lakesidemethodistchurch.org/f93c8855-f0a1-41e3-84d1-54812cd….js(hb.wpmucdn.com)
34 KB
1,080 ms
/lakesidemethodistchurch.org/5165bd8d-aa8c-46a6-8944-16e3399….js(hb.wpmucdn.com)
4 KB
630 ms

Should I go back to old plugin that was working or can I get assistance? The mobile pagespeed is unacceptable at 38. Desktop is 90 which is great.

This is the same site that had great results with WPMU before I migrated.

  • splaquet

    What were your stats with your old plugin?

    Did you take stats after removing the old one, before installing Hummingbird? If so, what were your stats before Hummingbird?

    And finally, what were your stats after Hummingbird? Are you using the CDN feature for CSS & JS?

    and lastly, sharing screenshots for reference (or a review URL) is *much* easier for any of us, as compared to what you have in your post.

  • splaquet

    For example...

    PageSpeed: (I noticed that you have mixed results when using http/https. You'll want to fix that in your end.)
    https://developers.google.com/speed/pagespeed/insights/?url=lakesidemethodistchurch.org&tab=desktop

    Here's your results on Pingdom:
    https://tools.pingdom.com/?_ga=2.223739675.1098822504.1544061250-1993380247.1539530686#59e04e7d59800000

    And here's your results on GTMetrix:
    https://gtmetrix.com/reports/lakesidemethodistchurch.org/NlyG4yTj#

    ###

    So, from what I can tell in these "real" results (as in, not copy/paste results that really doesn't mean anything without backing info), is that:
    - you don't have caching properly setup, more specifically cache expiration
    - you haven't removed query strings
    - your Avada theme assets (JS specifically) are causing hiccups. If you minified your CSS & scripts, I'd recommend rechecking your files.

    Something is certainly off with your theme assets... but again, without knowing what your original results were, (with your first optimization plugin, and without any performance plugin) we, as fellow community members, can't really offer insightful recommendations to help.

    Maybe that's why support couldn't help you out? Debuggers and troubleshooters need as much info as possible, if you expect resolution to issues.

    It'd be like taking your car to the auto mechanic and saying, "I was told this car would go 60mph, but since buying it, it's only going 30mph, TOPS!?! I've only driven it off the lot, through 2 blocks of rush hour traffic, and into my driveway... but it hasn't come close to 60mph!!!"

    "Have you considered taking it on the highway?"

    "Seriously?! You're not going to help me take my car to 60mph?!?"

    "Well, I'm honestly not sure that there's anything wrong with it. You've told me that you haven't even used your new car in an environment that allow 60mph, so maybe you should try that first. I'm only trying to help you out, because I'd feel horrible taking your money if there wasn't anything wrong."

    LOL... Well, maybe not exactly like that... but I started having fun with my little story :wink:

  • Nithin

    Hi michelle,

    If you are specially looking to fix render blocking resources, then is something which isn't possible to achieve a full score, because it entirely depends upon your theme, and how it honours Asset Optimizations done.

    What you could do is improve the render blocking resources score. At the moment the score for Desktop seems good. Render blocking will always have more issues on mobile, because the display view is much smaller, when compared to desktops. You'll need to find a way to only load assets that are required for that smaller view, without hampering the desktop layout, which is something complex to achieve, and it depends, and will vary upon different number of plugins running etc

    In Pagespeed tests you have a screenshot on the right, on how the page is rendered. Ideally you would only need to load enough CSS and JavaScript to render this part of the page, show it to the user, and only after that start loading everything else.

    What Hummingbirds Asset Optimization does is combine, and minify all the files into a single CSS, or JS file. However, moving everything into single CSS, or JS can break the design, or layout if the theme doesn't support it, so the plugin create multiple CSS, and JS files as listed below:

    https://hb.wpmucdn.com/lakesidemethodistchurch.org/fb49f81e-9ffe-493a-86f3-549b5ccae80c.css
    https://hb.wpmucdn.com/lakesidemethodistchurch.org/6bb2dfab-7292-48f4-b65a-f9ebe21b5753.css
    https://hb.wpmucdn.com/lakesidemethodistchurch.org/bed27acf-e6e9-4df6-978d-29e989aa0b9f.js

    This is what you are seeing in the Performance Test results, which means all the files are optimised, and is loading via the Hummingbird CDN. There isn't any way to exclude those listed compressed, and minified files, what you could do is try to reduce the number of .js, and .css files generated within Hummingbird by improving render blocking resources.

    The Basic rule of the thumb to improve render blocking resources is to move the files to the footer, I could notice you already have Advanced Mode in Asset Optimization enabled.

    So, in your Asset Optimization page:
    1) Go to the 1st file listed in the Asset Optimization page, enable "Compression" option for the 1st file,
    2) Load the frontend, and check whether the homepage design, or layout breaks
    3) If not, you can enable the "Combine" option, and then check the homepage, and see whether the layout breaks.
    4) If the layout breaks this time, you'll have to revert the "Combine" option, Save the changes, and move on with the next step which is "Move to footer", and check whether it breaks the style, if yes, revert if needed. Then carry the step 1 again for the next file, until you get an optimised result.

    The theme might break the frontend layout if all the files are move to footer, it'll require more of a trial, and error method to find the optimal configuration, and to see which all files needs to be moved to footer etc.

    I'm afraid, there isn't any specific steps we could pin point, as it entirely depends upon the theme, and the steps would vary from one theme to another due to this. What could be done is improve the existing score, which would require trial , and error method as mentioned above, and in turn will improve in both mobile, and desktop modes.

    You can check the following article on how to move forward with this:
    https://premium.wpmudev.org/blog/eliminate-render-blocking-issues-hummingbird/
    https://premium.wpmudev.org/docs/wpmu-dev-plugins/hummingbird/#chapter-4

    I hope this would help in optimising render blocking issue further. Have a great day ahead.

    Regards,
    Nithin

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.