<p>It tends to squeeze an extra 10-20% out of jpegs. Fantastic if you serve static jpeg tiles, for example.</p>
<p>We can always cross that bridge when we reach it if we ever have more than one jpeg on the website, and we can always start with slim PNGs first.</p>
<p>How do you think we should make this happen? First a PR on the chef recipes to install <code>advancecomp gifsicle jhead jpegoptim libjpeg-progs optipng pngcrush pngquant</code> (on which servers?), then a PR to <code>image_optim.yml</code> to enable them in the pipeline?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/pull/1691#issuecomment-347907000">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABWnLeTGEvT2SDhI4SAcczhEr6cyoNsdks5s7YAFgaJpZM4QuAHd">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABWnLRbVQNjpH2lp_lzJopNQW1hbhOgWks5s7YAFgaJpZM4QuAHd.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/openstreetmap/openstreetmap-website/pull/1691#issuecomment-347907000"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/openstreetmap/openstreetmap-website","title":"openstreetmap/openstreetmap-website","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/openstreetmap/openstreetmap-website"}},"updates":{"snippets":[{"icon":"PERSON","message":"@grischard in #1691: It tends to squeeze an extra 10-20% out of jpegs. Fantastic if you serve static jpeg tiles, for example.\r\n\r\nWe can always cross that bridge when we reach it if we ever have more than one jpeg on the website, and we can always start with slim PNGs first.\r\n\r\nHow do you think we should make this happen? First a PR on the chef recipes to install `advancecomp gifsicle jhead jpegoptim libjpeg-progs optipng pngcrush pngquant` (on which servers?), then a PR to `image_optim.yml` to enable them in the pipeline?"}],"action":{"name":"View Pull Request","url":"https://github.com/openstreetmap/openstreetmap-website/pull/1691#issuecomment-347907000"}}}</script>