Hi @wood1e,
You can try. There is no solution that fits all, and this is a trial and error process. Move one file to the footer, save the settings, check the frontend – if no errors, move another file.
I prefer to move everything to footer, then work my way on resolving errors. The files that cause most of the errors, when moved to footer, are jQuery related js files. So be careful with them.
Also, many themes/plugins have their own optimization options. So I would check those settings first.
Best regards,
Anton
Thread Starter
wood1e
(@wood1e)
Ok I will use trial and error.
Strange how most of the render blocking are your own files?
Why is that?
@wood1e,
What do you mean by “your own”? All these files are minified version of your assets. If you remove compression, they will be served uncompressed from their default locations (still be render blocking, though).
Best regards,
Anton
Thread Starter
wood1e
(@wood1e)
What I mean is Google speed test is showing that the majority of the render blocking is Hummingbird files.
So I just find it ironic that a plugin to speed up a site is according to Google, actually causing most of the render blocking
@wood1e,
Those are not Hummingbird files, they are your site files. For example, https://www.mobilityworld.co.uk/wp-content/uploads/hummingbird-assets/2e1728e983fa8ea3e2b008304615f77f-2.js is the compressed version of jquery-core file. Minified versions are stored in ‘/uploads/hummingbird-assets’ folder, but you can change that to any folder you want in the Asset Optimization settings. Hummingbird does not overwrite any core files, instead it stores compressed copies in the above location. So in case you decide you want to reset everything back to defaults, the copies are removed and you are left with the original files.
Best regards,
Anton
Thread Starter
wood1e
(@wood1e)
Sorry for the delay, I do not need to reset everything I am jsut wondering why Google would pick these up if they are compressed?
http://prntscr.com/jz61ua if these are all compressed why would they still remain render blocking?
Hi @wood1e,
Compressing a file doesn’t mean it will fix the render blocking, it will reduce the file size which makes it faster to load.
For more information on optimizing CSS delivery see https://developers.google.com/speed/docs/insights/OptimizeCSSDelivery
For the CSS you can try turning on the inline CSS option for your smaller CSS files and load some of your CSS files in the footer, these options are available in the advanced area of Hummingbirds Asset Optimization.
For more information on removing render blocking JS see https://developers.google.com/speed/docs/insights/BlockingJS
Again you can turn on defer JS option in the advanced area of Hummingbirds Asset Optimization.
For both your JS and CSS files I would change settings one file at a time and check the front end of your site to make sure nothing is breaking.
It’s hard to get a perfect performance score and fix all recommendations especially when you are using multiple plugins that require different JS and CSS files.
After looking up your site on Google PageSpeed Insights, you already have quite a decent score so I wouldn’t be too worried about getting it much higher.
Cheers,
Calum Brash
