Back in Web 1.0 days, getting image file sizes as low as possible was critical. Good thing we’re not there anymore, but that doesn’t mean getting file sizes down is no longer a concern. Why?
You want your site’s pages to load as fast as possible for visitors. Every split-second you can keep their short, impatient attention spans from clicking away, counts. And you’ve probably got more than just the one graphic on the page. Maybe you even have a lot of visitors—a server repeatedly tossing out large files again and again and again isn’t going to be a happy peak performing little server.
It’s just plain silly not to get those image file sizes as small as you can get them. Especially with resources like TinyPNG around, which will do that file size shrinking for free. TinyPNG itself is about as easy to use as it gets (visit the site, then just drag-and-drop the image you want to shrink), and works with three of the most popular Web image file formats: PNG, JPEG, and WebP.
“But quality degrades!” you argue. Technically, yeah, but can you really see the difference? Or even in those rare instances where there may be some discernable visual degradation, does it really matter to your visitors?
Here’s a test and example. The first image is the original I just picked up from Pixabay. It’s 316K. The image next to it is after running it through TinyPNG. It’s now 80.6K, getting rid of almost 75% of that file size load! Click on the images to view each full-sized in separate lightboxes, and compare.
It’s a n0-brainer tool to use, frankly.