Do you know the one tool that I hate more than any other by Google? Well, it should be no surprise to page speed junkies, it is Google PageSpeed Insights.
It is a simple tool (seemingly) to help webmasters, developers and normal people analyze their website for speed. You see, web performance is officially a search ranking factor, so Google has this tool by which they score websites out of 100. While it seems to have been built to help developers, etc., for me it seems to have been built to frustrate and torture page speed junkies. Especially freelancers are more frustrated because of this tool.
The problem is that – clients want 100/100, which is not possible in most cases unless your website is but an HTML skeleton. I don’t blame these guys for wanting that score. It’s that 100/100 is mostly not possible, because there always comes a point after which any speed optimization will break the site. Now… unless you want a broken site with 100/100, I can give you that. But if you want 100/100 but nothing broken, you’re mistaken to think that it is possible. We, page speed junkies, do not possess some magic wand that we can just wave around and your site suddenly scores 100/100.
PageSpeed Insights detects the tiniest possible unsolvable issues and scores on that basis. Even if major issues like leverage browser caching, gzip compression, image optimization are taken care of, the score does not improve as much as it will be affected by unsolvable issues. I don’t understand why some 50KBs JS files have more effect on score than leverage browser caching of 50+ files? Unfair, of course!