Did you know that the shortest valid piece of HTML5 is <!doctype html><title>x</title>? See for yourself at the W3C Validator!
Minify is a minifier package written in Go. It provides HTML5, CSS3, JS, JSON, SVG and XML minifiers and an interface to implement any other minifier. Minification is the process of removing bytes from a file (such as whitespace) without changing its output and therefore shrinking its size and speeding up transmission over the internet and possibly parsing. The implemented minifiers are designed for high performance.
The core functionality associates mimetypes with minification functions, allowing embedded resources (like CSS or JS within HTML files) to be minified as well. Users can add new implementations that are triggered based on a mimetype (or pattern), or redirect to an external command (like ClosureCompiler, UglifyCSS, ...).
Use ASM/SSE to further speed-up core parts of the parsers/minifiers
Improve JS minifiers by shortening variables and proper semicolon omission
Speed-up SVG minifier, it is very slow
Proper parser error reporting and line number + column information
Generation of source maps (uncertain, might slow down parsers too much if it cannot run separately nicely)
Create a cmd to pack webfiles (much like webpack), ie. merging CSS and JS files, inlining small external files, minification and gzipping. This would work on HTML files.
Prologue
Minifiers or bindings to minifiers exist in almost all programming languages. Some implementations are merely using several regular expressions to trim whitespace and comments (even though regex for parsing HTML/XML is ill-advised, for a good read see Regular Expressions: Now You Have Two Problems). Some implementations are much more profound, such as the YUI Compressor and Google Closure Compiler for JS. As most existing implementations either use JavaScript, use regexes, and don't focus on performance, they are pretty slow.
This minifier proves to be that fast and extensive minifier that can handle HTML and any other filetype it may contain (CSS, JS, ...). It is usually orders of magnitude faster than existing minifiers.
Installation
Make sure you have Git and Go (1.13 or higher) installed, run
mkdir Project
cd Project
go mod init
go get -u github.com/tdewolff/minify/v2
Then add the following imports to be able to use the various minifiers
$ docker run -it tdewolff/minify
/ # minify --version
API stability
There is no guarantee for absolute stability, but I take issues and bugs seriously and don't take API changes lightly. The library will be maintained in a compatible way unless vital bugs prevent me from doing so. There has been one API change after v1 which added options support and I took the opportunity to push through some more API clean up as well. There are no plans whatsoever for future API changes.
Testing
For all subpackages and the imported parse package, test coverage of 100% is pursued. Besides full coverage, the minifiers are fuzz tested using github.com/dvyukov/go-fuzz, see the wiki for the most important bugs found by fuzz testing. These tests ensure that everything works as intended and that the code does not crash (whatever the input). If you still encounter a bug, please file a bug report!
Performance
The benchmarks directory contains a number of standardized samples used to compare performance between changes. To give an indication of the speed of this library, I've ran the tests on my Thinkpad T460 (i5-6300U quad-core 2.4GHz running Arch Linux) using Go 1.15.
KeepDefaultAttrVals preserve default attribute values such as <script type="application/javascript">
KeepDocumentTags preserve html, head and body tags
KeepEndTags preserve all end tags
KeepQuotes preserve quotes around attribute values
KeepWhitespace preserve whitespace between inline tags but still collapse multiple whitespace characters into one
After recent benchmarking and profiling it became really fast and minifies pages in the 10ms range, making it viable for on-the-fly minification.
However, be careful when doing on-the-fly minification. Minification typically trims off 10% and does this at worst around about 20MB/s. This means users have to download slower than 2MB/s to make on-the-fly minification worthwhile. This may or may not apply in your situation. Rather use caching!
Whitespace removal
The whitespace removal mechanism collapses all sequences of whitespace (spaces, newlines, tabs) to a single space. If the sequence contained a newline or carriage return it will collapse into a newline character instead. It trims all text parts (in between tags) depending on whether it was preceded by a space from a previous piece of text and whether it is followed up by a block element or an inline element. In the former case we can omit spaces while for inline elements whitespace has significance.
Make sure your HTML doesn't depend on whitespace between block elements that have been changed to inline or inline-block elements using CSS. Your layout should not depend on those whitespaces as the minifier will remove them. An example is a menu consisting of multiple <li> that have display:inline-block applied and have whitespace in between them. It is bad practise to rely on whitespace for element positioning anyways!
CSS
Minification typically shaves off about 10%-15%. This CSS minifier will not do structural changes to your stylesheets. Although this could result in smaller files, the complexity is quite high and the risk of breaking website is high too.
The CSS minifier will only use safe minifications:
remove comments and unnecessary whitespace (but keep /*! ... */ which usually contains the license)
remove trailing semicolons
optimize margin, padding and border-width number of sides
shorten numbers by removing unnecessary + and zeros and rewriting with/without exponent
remove dimension and percentage for zero values
remove quotes for URLs
remove quotes for font families and make lowercase
rewrite hex colors to/from color names, or to three digit hex
rewrite rgb(, rgba(, hsl( and hsla( colors to hex or name
use four digit hex for alpha values (transparent → #0000)
replace normal and bold by numbers for font-weight and font
replace none → 0 for border, background and outline
lowercase all identifiers except classes, IDs and URLs to enhance gzip compression
shorten MS alpha function
rewrite data URIs with base64 or ASCII whichever is shorter
calls minifier for data URI mediatypes, thus you can compress embedded SVG files if you have that minifier attached
shorten aggregate declarations such as background and font
It does purposely not use the following techniques:
(partially) merge rulesets
(partially) split rulesets
collapse multiple declarations when main declaration is defined within a ruleset (don't put font-weight within an already existing font, too complex)
remove overwritten properties in ruleset (this not always overwrites it, for example with !important)
rewrite properties into one ruleset if possible (like margin-top, margin-right, margin-bottom and margin-left → margin)
put nested ID selector at the front (body > div#elem p → #elem p)
rewrite attribute selectors for IDs and classes (div[id=a] → div#a)
put space after pseudo-selectors (IE6 is old, move on!)
There are a couple of comparison tables online, such as CSS Minifier Comparison, CSS minifiers comparison and CleanCSS tests. Comparing speed between each, this minifier will usually be between 10x-300x faster than existing implementations, and even rank among the top for minification ratios. It falls short with the purposely not implemented and often unsafe techniques.
Options:
KeepCSS2 prohibits using CSS3 syntax (such as exponents in numbers, or rgba( → rgb(), might be incomplete
Precision number of significant digits to preserve for numbers, 0 means no trimming
JS
The JS minifier typically shaves off about 35% -- 65% of filesize depening on the file, which is a compression close to many other minifiers. Common speeds of PHP and JS implementations are about 100-300kB/s (see Uglify2, Adventures in PHP web asset minimization). This implementation is orders of magnitude faster at around ~25MB/s.
The following features are implemented:
remove superfluous whitespace
remove superfluous semicolons
shorten true, false, and undefined to !0, !1 and void 0
rename variables and functions to shorter names (not in global scope)
move var declarations to the top of the global/function scope (if more than one)
collapse if/else statements to expressions
minify conditional expressions to simpler ones
merge sequential expression statements to one, including into return and throw
remove superfluous grouping in expressions
shorten or remove string escapes
convert object key or index expression from string to identifier or decimal
merge concatenated strings
rewrite numbers (binary, octal, decimal, hexadecimal) to shorter representations
Options:
KeepVarNames keeps variable names as they are and omits shortening variable names
Precision number of significant digits to preserve for numbers, 0 means no trimming
Comparison with other tools
Performance is measured with time [command] ran 10 times and selecting the fastest one, on a Thinkpad T460 (i5-6300U quad-core 2.4GHz running Arch Linux) using Go 1.15.
Closure Compiler: closure-compiler -O SIMPLE --js script.js --js_output_file script.min.js --language_in ECMASCRIPT_NEXT -W QUIET --jscomp_off=checkVars optimization level SIMPLE instead of ADVANCED to make similar assumptions as do the other tools (do not rename/assume anything of global level variables)
Compression ratio (lower is better)
All tools give very similar results, although UglifyJS compresses slightly better.
Tool
ace.js
dot.js
jquery.js
jqueryui.js
moment.js
minify
53.7%
64.8%
34.2%
51.3%
34.8%
esbuild
53.8%
66.3%
34.4%
53.1%
34.8%
terser
53.2%
65.2%
34.2%
51.8%
34.7%
UglifyJS
53.1%
64.7%
33.8%
50.7%
34.2%
Closure Compiler
53.4%
64.0%
35.7%
53.6%
34.3%
Time (lower is better)
Most tools are extremely slow, with minify and esbuild being orders of magnitudes faster.
Tool
ace.js
dot.js
jquery.js
jqueryui.js
moment.js
minify
49ms
5ms
22ms
35ms
13ms
esbuild
64ms
9ms
31ms
51ms
17ms
terser
2900s
180ms
1400ms
2200ms
730ms
UglifyJS
3900ms
210ms
2000ms
3100ms
910ms
Closure Compiler
6100ms
2500ms
4400ms
5300ms
3500ms
JSON
Minification typically shaves off about 15% of filesize for common indented JSON such as generated by JSON Generator.
The JSON minifier only removes whitespace, which is the only thing that can be left out, and minifies numbers (1000 => 1e3).
Options:
Precision number of significant digits to preserve for numbers, 0 means no trimming
KeepNumbers do not minify numbers if set to true, by default numbers will be minified
SVG
The SVG minifier uses these minifications:
trim and collapse whitespace between all tags
strip comments, empty doctype, XML prelude, metadata
strip SVG version
strip CDATA sections wherever possible
collapse tags with no content to a void tag
minify style tag and attributes with the CSS minifier
minify colors
shorten lengths and numbers and remove default px unit
shorten path data
use relative or absolute positions in path data whichever is shorter
TODO:
convert attributes to style attribute whenever shorter
merge path data? (same style and no intersection -- the latter is difficult)
Options:
Precision number of significant digits to preserve for numbers, 0 means no trimming
XML
The XML minifier uses these minifications:
strip unnecessary whitespace and otherwise collapse it to one space (or newline if it originally contained a newline)
strip comments
collapse tags with no content to a void tag
strip CDATA sections wherever possible
Options:
KeepWhitespace preserve whitespace between inline tags but still collapse multiple whitespace characters into one
Usage
Any input stream is being buffered by the minification functions. This is how the underlying buffer package inherently works to ensure high performance. The output stream however is not buffered. It is wise to preallocate a buffer as big as the input to which the output is written, or otherwise use bufio to buffer to a streaming writer.
New
Retrieve a minifier struct which holds a map of mediatype → minifier functions.
Minify resources on the fly using middleware. It passes a wrapped response writer to the handler that removes the Content-Length header. The minifier is chosen based on the Content-Type header or, if the header is empty, by the request URI file extension. This is on-the-fly processing, you should preferably cache the results though!
Using the params map[string]string argument one can pass parameters to the minifier such as seen in mediatypes (type/subtype; key1=val2; key2=val2). Examples are the encoding or charset of the data. Calling Minify will split the mimetype and parameters for the minifiers for you, but MinifyMimetype can be used if you already have them split up.
Minifiers can also be added using a regular expression. For example a minifier with image/.* will match any image mime.