[Hummingbird] Google PageSpeed Insights

My client's score on PageSpeed Insights is really poor.
Is there anything more we can do in Hummingbird, or is this just a problem with the theme?
I've compressed images, tried to move all of the JS files to the footer and done other things, but the score is still crap in mobile view. (Desktop is not too bad.)

  • Brad Jones

    First things first...

    walking-dog-leash.jpg = 517 KB
    slide1.jpg = 473 KB
    o-DOG-facebook.jpg = 419 KB
    dogwomangrass1.jpg = 325 KB

    Those 4 images alone are a big problem. Have you used Super Smush? Getting those pic sizes under control will make a huge difference...

    Also take a look at https://www.seoptimer.com/nikkiscollarclub.com there are some recommendations here as well...Have you used any of the recommendations in Hummingbird?

  • Steve McGough

    I was certain that I already ran Super Smush in bulk all the way through everything? Maybe I just have to pull the image and do it in PhotoShop?

    I even had moved a bunch of JS files to the footer in Hummingbird the other day, but GTMetrix still reads them as not in the footer?

    I think I did go through the recommendations in HB and I had someone from your team looking at it the other day too.

  • Steve McGough

    Caching on. GZIP compression active. Images crunched quite a bit. The stuff HB is calling out are small images in the Byte range, not even KB.
    Move all of the JS stuff that we could to the footer. Some can not be moved or must stay up near the top of the page.
    Performance test in HB currently at 87/100. You'd think that would be good.

    But the reports we're getting for mobile are pretty bad...

    GTmetrix is calling out a bunch of JS files it says needs to be moved to the footer, but many are already moved in Hummingbird settings.

    PageSpeed Insights...

    The size of the images have been very compressed, so I think we are good there. Maybe it's just the size of the page and the combination of images?

  • Adam Czajczyk

    Hi Steve McGough

    I hope you're well today and thank you for your question!

    I checked your site and I think Brad is right (thanks Brad Jones for jumping in!) and it would be good to start with those images.

    If you look closer at the file names, those images are original "full size" images. By default, when you upload an image to WordPress, WordPress creates additional images of various sizes out of it but it also stores the original one. Smush, by default, doesn't process these original images as they are also rarely used on sites. But sometimes they are.

    You can easily recognize those "original images" because they do not have a "size suffix" appended to the file name. So for example "image.jpg" is an original image while "image-200x300.jpg" is one created additionally by WordPress.

    I checked current settings of Smush on your site and it's not set to process those original images so you might want to start with that: enable at least "Smush my original full size images" options and run bulk smush again. It will skip already optimized images but will optimize those big original ones.

    The second thing to start with would be Asset Optimization. I can see that you have moved most of the JS files to the footer but that's only a part of entire optimization. CSS files are not "configured" at all (so they are "as they are" by default) and JS files are also not combined and not forced to load after the page has been loaded.

    Therefore, it would be worth to try to set that up. I don't recommend enabling all options for all the files at once as this might actually cause the site to break to the point that entire Asset Optimization configuration would have to be started from scratch so I'd rather suggest this way:

    - take one, two files from the top of the list (go through all CSS and JS files subsequently)
    - enable "combine" option for them
    - check if site's running fine; if not, experiment with that option for these files until it does
    - repeat that for next files on the list

    - once that's done, repeat that process with "move to footer" option for all CSS files

    - after that with "inline" option for all CSS files

    - after that with "force load after the page is loaded" for JS files

    Then once all that is done, check how the page performs and what are the scores and I believe it should be better. Then, if necessary, we'll consider further steps :slight_smile:

    Best regards,

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.