It would be interesting to benchmark the CPU performance of a full page load and paint for each version. At the end of the day the language parser will see the

It would be interesting to benchmark the CPU performance of a full page load and paint for each version. At the end of the day the language parser will see the decompressed text, so the minified version should reduce the time spent in that stage. However AFAIK a basic minify, that only compresses whitespace and identifiers, would only speed up the lexer, which I expect is the fastest part anyway. But reducing the number of actual CSS rules (as the author experiments with manually) may make a measurable difference fwiw I don't bother minifying anything on my personal site. I realise that complex sites can have large enough payloads to make it worth it, especially for Javascript, but for the typical developer blog it's likely overengineering in the extreme. If I were to apply any postprocessor it would probably be a prettifier, for the HTML, since the template substitution results in mismatched indents. But then again anyone looking at the DOM is likely to be doing it in the dev tools, which already renders a projectional view, rather then the original source