Images make up a majority of web content.But a lot of websites and applications that we browse aren’t always delivering the most optimal image format, size, quality and dimension.…
As a developer, it seems inefficient to serve a 2000kb JPEG image when we could compress images to optimize the performance without degrading the visual quality.
We are not new to this kind of responsibility. But our productivity will end up being questioned if we do not deliver fast. In order to do so, the community has devised several patterns to help improve productivity. Let’s review few of these patterns based on their categories:
- Optimized formats
- Third-party Libraries
- Third-party APIs
It is natural to use image formats such as PNG, JPEG and GIF. These three have been around for several years, but they each have characteristics that would make you choose one over another in certain cases. Additional formats have been introduced and some are being standardized in order to provide a better way to serve images in their best optimization level.
These optimized formats are, as a matter fact, a very good attempt at reducing the image bloat. Image formats are the means for achieving convenient optimization and compression without resorting to third-party solutions. Unfortunately, the image format battle continues, as there is inadequate support across all browsers, limitations, policies and other factors that make it hard to ensure every image format is consistently optimized.
You can also use third-party libraries to compress images. These libraries provide an exposed API method to which you can pass your image file, specify some compression argument, and have a compressed image returned for your configuration.
There is nothing wrong with writing your own solution, but we are trying to save time as well. These libraries are written based on some standard algorithms so it’s fine to rely on them to some extent. However, they may not give you enough flexibility in terms of how compression is handled. It’s hard to find a third-party library that takes a PNG file and delivers an optimally compressed lossless image.
There are public and premium third-party APIs that could be used to process a bloated image, which is then returned to you as an HTTP response. This so far is the most easier to use because it just requires basic knowledge of HTTP to get your images compressed. It’s not language or platform dependent which makes it a little more flexible than the others.
Plus, you encounter the same issue as you do with third-party SDKs: It’s hard to find that all-in-one-solution that is flexible enough to address your problem.
While the platforms discussed above are commonly used for compressing images, not one offers a comprehensive, intelligent solution for compression and optimization. Image delivery and upload may even become more complex when you need to serve your images via a content delivery network (CDN). This adds another layer of complexity to the problem.
But, what if there was a single tool that could:
- Upload, store and deliver images via CDN
- Transform images (dimension, color adjustment, etc)
- Compress images losslessly
Cloudinary is that solution. It’s a comprehensive image management tool that quickly and easily addresses your image concerns, eliminating the challenges and risks of image storage and management.
Cloudinary also intelligently addresses our image compression challenges. It uses image transformation features to give you control over the quality of your images, while giving you the option to automatically select quality and format.
What’s most interesting about Cloudinary is that all these features are URL-based, which means you simply need to alter the URL to achieve the configurations you need. You also can use the provided SDKs if you prefer not to do URL manipulation.
The following image of a woman was delivered using Cloudinary (the upload mechanism is not covered but you can read about that here):
It’s delivered with this URL:
This image weighs about 569kb. This is not a bad quality, but we can do better. Let’s see how much we can adjust this image without losing visual quality:
q transformation property takes a variety of values, one of which is a range of 1 to 100 that indicates the quality in percentages. This is what we have applied above and the image was trimmed down to 123kb. We just eliminated 446kb, which is a great example of what we mean by the title of this article: “Your Web Image is Unnecessarily Bloated.”
Let’s go hard on this image and see what’s the worst that can happen:
I just took the quality down to 40 and trimmed down the size to 38kb, yet the visual quality of the image is partially degraded. By now you could imagine the bandwidth you’d be wasting because of the lack of compression.
Let’s try 10 percent.
Now the image is visually poor. This doesn’t mean we can tell for sure that 40 percent is the perfect point. It could be 30, it could be 20, but we don’t know exactly To find a perfect quality, we can use the
auto quality value rather than a rigid value:
The auto value produces an image that weighs 45kb. This is easier and quicker than using a rigid value and guessing the perfect compression rate.
In addition to quality transformations, you also can define automatic transcoding for your images. This enables Cloudinary to choose a suitable, and optimal, image format for the browser rendering the image:
Browsers, such as Chrome, support specific formats, like WebP, to improve performance . Cloudinary always knows when and how best to do this without losing the visual quality of the image.
You website images might be bloated or optimized to a certain level. You can use image formats, third-party libraries and APIs to optimize images, but they might not be as flexible as you need them to be.
Cloudinary offers a comprehensive image management solution that delivers and transforms images via URL-based APIs. You can utilize the transformation features for image optimization and compression.
You can sign up for a free Cloudinary account and see how easy it is to optimize images with its URL-based solution.
This post was originally published on Noupe.com