"Two tests are run: One exclusively applying HTML minification (with the most aggressive settings that do not impact conformance), the other enabling all minification features the respective minifier offers (this is play-it's not a fair comparison and may exceed project needs)."
"Failed sites are not excluded from the calculation for the average result, but counted as unminified. This avoids test failures advantaging the respective minifier."
"HTML Minifier Terser is currently not included due to issues around whitespace collapsing and removal of code using modern CSS features, issues which appeared to distort the data."
A collection of regularly updated benchmarks evaluates HTML minifiers by measuring their compression effectiveness in bytes. Two distinct testing approaches are employed: one applies HTML minification exclusively with aggressive settings that maintain conformance, while the other enables all available minification features each tool offers. The benchmarks exclude HTML Minifier Terser due to whitespace collapsing issues and CSS feature incompatibilities that distorted results. Failed sites are counted as unminified rather than excluded, preventing test failures from artificially advantaging specific minifiers. Calculations rely on byte comparisons to determine effectiveness. Currently, benchmarks are executed manually on a 2024 Apple Mac Mini, though automation is planned for future updates.
#html-minification #performance-benchmarks #compression-comparison #web-optimization #minifier-evaluation
Read at GitHub
Unable to calculate read time
Collection
[
|
...
]