urn:uuid:397a5b06-5fb3-5931-9266-c0e2ba0bfab6 Topic: Compression – Ctrl blog Daniel Aleksandersen https://www.daniel.priv.no/ Copyright © 2022 Daniel Aleksandersen. https://www.ctrl.blog/assets/logo/logo-square.svg 2022-06-21T03:00:00Z weekly 10 urn:uuid:d4d4f6b1-d758-4f25-b819-40c9caa6c256 2021-11-26T12:09:00Z 2021-11-26T12:09:00Z Bitrot resistance of next-generation image formats Bitrot happens. So, what happens when I flip one random bit in AVIF and JPEG XL images. Improved data packing means less redundancy and more corruption. <p>I’ve compared two next-generation image formats, AVIF and JPEG XL (JXL), to see which best handles a random single corrupted bit. A meaningless exercise? Possibly. But half a picture of your beloved grandma is better than no picture at all.</p> <p><a href="https://www.ctrl.blog/entry/bitrot-avif-jxl-comparison.html">Read more …</a></p> urn:uuid:d0ce79bc-2bd2-4db3-9ec9-0b8c72479f96 2021-06-28T07:38:00Z 2022-06-21T03:00:00Z Does the web still need HTTP Deflate? The compression format war of the last decade was won by Gzip. Why do web browsers still support the legacy HTTP Deflate (Zlib) format? It’s time to deprecate it. <p>Compressing webpages to make them smaller is crucial to ensure fast webpage load times. Gzip and Brotli are the web’s two most used compression formats. A third contender, HTTP Deflate, has been around as long as Gzip, but it never caught on. Do you still need to support it on your websites and apps? or is it time to retire HTTP Deflate from the web platform?</p> <p><a href="https://www.ctrl.blog/entry/http-deflate-compression.html">Read more …</a></p> urn:uuid:efb19ac5-2bd1-4df5-9732-19ccb34dce9b 2020-07-14T02:26:00Z 2020-07-14T02:26:00Z Comparing file sizes of lossless WebP vs FLIF vs PNG The FLIF lossless image format makes big claims on file size savings, but lossless WebP actually delivers smaller lossless image files. <p>Last weekend, I compared two lossy image formats: AVIF and WebP. Today, I’m comparing the file size reduction of two lossless formats — FLIF and lossless WebP — compared to heavily optimized PNG images.</p> <p><a href="https://www.ctrl.blog/entry/webp-flif-comparison.html">Read more …</a></p> urn:uuid:f115568e-4164-4fa9-9e28-86736ac175a5 2019-10-15T06:02:00Z 2019-10-15T06:02:00Z Optimize your <head> metadata for better compression Optimize your <code translate="no">&lt;head&gt;</code> metadata for better compression Reduce the file size of compressed webpages by optimizing the order of <meta> and <link> elements in the document <head> section. <p>HTML Tidy can clean-up HTML documents by normalizing them, stripping comments, sorting element attributes alphabetically, and outputting consistent pretty-printed markup. The result is an HTML document with less unique data with more consistent and repeating patterns. This yields improved Gzip/DEFLATE compression-rates compared to a less neatly organized documents.</p> <p><a href="https://www.ctrl.blog/entry/html-meta-order-compression.html">Read more …</a></p> urn:uuid:46da4787-40b2-40ce-ad56-22dfcbf00075 2019-06-12T05:23:00Z 2019-06-12T05:23:00Z Compressed favicons are 70% smaller but 75% are served uncompressed The majority of websites don’t compress their favicon files despite an impressive average file size reduction of over 70 %. <p>Conventional wisdom for performance optimization says that you should only enable HTTP content negotiated compression for plain text data formats and leave it off for binary data formats. Many binary image formats natively support compression so there would be little gained from compression them again. However, there are a number of exceptions to this rule and one of them is the ubiquitous <code>favicon.ico</code> file.</p> <p><a href="https://www.ctrl.blog/entry/favicon-compression.html">Read more …</a></p>