So don’t go throwing away Kraken, Imagify, or Smush just yet… Especially if you post a lot of galleries. In its current form, however, it takes way too long to act as an efficient enough batch processor for small, independent publishers. I saw anywhere from a 74.63% to 89.28% decrease in size from my original image with very few visual artifacts. And it does do a great job compressing things. And while the output of ImageOptim’s lossy compression isn’t near as sharp, it’ll still be “good enough” for most folks.Īt the end of the day, Guetzli’s output is really nice. ![]() Doing both of those took me less than 2 minutes, combined. Included in the link above are 2 versions (lossless, and lossy) of the same image run through ImageOptim on macOS. If you’re interested in seeing how things panned out, here’s the output: During these runs, the server routinely went into swap. Why 84%? Well, that’s the lowest the Guetzli binary will let you go without editing the source and recompiling.Įach run (compressing a single image) took about 20 minutes on a medium sized cloud instance with 8GB of RAM. I ran a few (incredibly unscientific) tests on Google’s new Guetzli JPEG encoder last night at 100%, 90%, and 84% compression. Considering the last post I did here was in March, probably not. Maybe I’ll digest things a bit more and write about all of this later. And because I’m not really interested in tying my disjointed ideas together right now, I’ll spare everyone the word salad and post a GIF of how I’m feeling instead. The previous revisions of this draft post go to some really weird places. So exciting that I don’t even know what else to say without turning this into a big, rambling, 4500-word post. However, when the opportunity came to work with the team that Chris Lema has put together, I couldn’t pass it up. ![]() I’m incredibly proud of what they’ve been able to build, as well as the hand that I’ve had in helping to do that. In the five and a half years that I’ve been there, we’ve managed to grow the company from five employees in Austin (with me working remotely) to over four hundred and fifty across five offices in the US and Europe. The decision to leave WP Engine was hard. It’s an opportunity for me to get out of Marketing-where I’ve been broadening my skillset since last fall-and back into implementing things that impact users. In just a couple weeks, I’ll be joining the Managed WordPress team at Liquid Web as their Senior Performance Engineer. I know things are normally pretty quiet around here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |