Varnish Cache and Brotli compression
If it can do gzip, it should be able to do brotli as the HTTP-header &quot;handshake&quot; for both is identical, just use &quot;br&quot; instead of &quot;gzip&quot;.<p>I&#x27;ve been seeing a lot of threads about Brotli lately and having experimented with it thoroughly at work (large social network let&#x27;s say) and having ramped it up to 100% on production, I would say the benefit over Gzip is marginal and often not worth the increase in latency due to the compression taking longer offsetting your benefits. Of course you can compress once and cache but then there is the cost of storing multiple compressed copies.<p>SDCH is honestly a lot more promising and we are seeing notable improvements in page load times, on both dynamic and static content. That&#x27;s ramped at around 10% in production and if things go as expected we will be at a 100% in production rather soon, and write a blog post on it. So far we are seeing 10% improvement in page load times in the United States, and 30% in India, Bangladesh, Vietnam etc. and compressing the content about 50% more compared to just gzip when we are using sdch+gzip. This is all achieved with a dictionary smaller than 700kB.