: Minifying HTML = negative impact on Google Pagespeed Google Pagespeed says that we should minify our HTML-output. So we did this (using Minify-library and Minify_HTML::minify($content);) The warning

@Mendez628

The only explanation I can think of is that the variance in other factors might have been behind this.

Could have been anything, but one thing that comes to mind is that the server response time increased because of the time required to minify html on the fly. If, for example the server response time increased from 0.05s to 0.15s, the total pagespeed could have been worse off than without html minification, except the rule for server response time still didn't fire (because it only displays when the server response time jumps above 0.2s).

Also, the warning for render-blocking resources switched from "should fix" to "must fix", which indicates that something else is indeed going on behind the scenes. But like I said, based on the screenshots you provided, I have no way of knowing what exactly that could be.

Vote Up Vote Down

@Alves908

Pagespeed is a guide not a rulebook. Aiming to get 100/100 means you've followed a guide to serving a better site but it by no means translates into Google giving you higher metrics for rankings.

Even worse, Google's own products very often break the guide they set out. Some of their best practices (Google CDN delivered js files) also break the Pagespeed guide (not minified).

Take it as advisory and create your own tests based on known metrics for performance:


How easy to use is your site?
How fast is the page/DOM loading?
How does that vary depending on location?

Vote Up Vote Down