Insights to PageSpeed insights

Google is lying to us all.

That may seem like a harsh statement, but it’s very true. Google, with the use of it’s PageSpeed insights tool (https://developers.google.com/speed/pagespeed/insights/) is making hard working developers like myself go crazy optimizing their websites.

Case in point: for the past 2 days, I’ve been trying to increase a client’s pagespeed score. I’ve even gone so far as to write a CSS caching mechanism in PHP which combines and minifies all of the CSS used by the site.

And now I can choose to either compress or cache the result.

No matter what I seem to try, with the combination of nginx and apache included, to both compress and cache this generated file. I’ve been able to get a score of 79/100 when using caching, or 83/100 when using compression. But when I use one method, it complains about the other not being used.

And then, there is the always-a-pain-in-the-ass, “Eliminate render-blocking JavaScript and CSS in above-the-fold content” problem.

I got to the point of running PageSpeed insights on www.google.com, and now, I don’t feel so bad. You see, Google’s own main website, that simple and basic Google Search page, only get’s a 64/100 for the mobile tab.

Google's PageSpeed Insights for Google.
Google’s PageSpeed Insights for Google.

So, web developers of the world trying to measure up to that supposed impossible to reach 100/100 for speed, don’t feel bad.

Chances are, you are doing better then Google themselves.