Optipng

[benfoxall]

(note - this is branched from #41)

I'm not sure if this is very necessary - but it runs the favicon images through optipng which would reduce the size.

pros:

• ~%30 filesize reduction

cons:

• slower response times
• potentially awkward for deploy/dev - adds a couple of dependencies with os-specific binaries
• it's already a pretty tiny file - doesn't make much difference overall

When I tested locally:

before: 8.1k ~100ms after: 5.7k ~200ms

… so it's pretty negligible (especially because the files are downloaded in the background). Though if you're wanting to hyper-optimise network, then maybe it'll help.

[danielthepope]

Now this is an interesting idea. Since I want to continue serving files whenever possible (as mentioned in #41), perhaps you could pipe through OptiPNG before saving the file to disk? The first time an icon is requested it'll take a bit longer to be delivered, but after the first request the file delivery will be quicker than it currently is. Once upon a time I had an idea to preemptively generate icons before they're requested (#18), so this would eliminate the delay caused by generating the icon in the first place