This project uses HTMLMinifier, optipng, and zopfli to create a custom production Elm build pipeline. You can see how I make use of these tools in this build script. Here are the results in case you're interested. I used the same ideas from this project to build and deploy dwayne/elm-conduit, which you can learn more about in my article Yet Another Tour of an Open-Source Elm SPA. - Source: dev.to / 26 days ago

Did you compare to PNG crush and optipng? Those are what I used to use because they're easily installable Linux/brew packages. Source: about 1 year ago

Assuming your frames are PNG files, you could use a lossless optimizer like optipng to try if their size can be reduced. I prefer oxipng, which is faster and multithreaded, and seems to have more active development. Source: over 2 years ago

I've tried a few, the best one was pingo (https://css-ig.net/pingo). Pingo -s9 gives better results than oxipng with Zopfli, while being usually two order of magnitudes faster. It's also faster than "regular" oxipng while being better. I can usually shave of 15%/20% of the size of png files I encounter. One thing I didn't check is that you might pay that in decoding time, I've never seen anybody talking about that... - Source: Hacker News / almost 2 years ago

Pinga, GUI for Pingo (https://css-ig.net/pingo) for lossless photo compression while keeping the metadata. Source: almost 3 years ago