Scoring 100 on Mobile and Desktop in Google Pagespeed Insights can be a daunting task. Once you use a JS framework you’re pretty much screwed because of the “above-the-fold” render blocking thing.
But is it really important to score 100? In which cases should you worry about the score? There’s heaps of articles suggesting “stop worrying about the pagespeed insights score”. Well, I agree that it might not be the most important factor for the user experience. But on the other hand, I don’t agree that it’s not important to Google. A Google employee told me during an AdWords campaign (set up by Google themselves), that our Mobile page speed was low and that this was penalized by the Search Engine. And how did he measure it? With Google Page Speed Insights, of course. See, the point is, if Google Page Speed Insights is good or bad is not important. It matters to Google, so it matters for your SEO.
It’s a bit hard to design an experiment to actually show the impact of an increased page speed insights score. What I could think of was this: Write an article and publish it twice, once with a bad page speed score, and once with a good one. So here’s the article, it’s about Angular Universal:
and here’s the article again, just loading slower since I load five unnecessary versions of Jquery in the head:
The first article scores 99/100 (mobile) and 100/100 (desktop) and the second article 61/100 (mobile) and 75/100 (desktop). Let’s see what happens, I’ll post the result in a few weeks here.
Google currently only lists the slower article. No idea why. Maybe it thinks it must be really awesome if 5 versions of jquery are required?
By the way, the article is also related to this topic, since Angular Universal would be the answer to page speed problems. Well, you know, if it’d actually work (read the article).