In this blog, I’ll share a valuable shortcut that can help you turn all images responsive. But first, let’s talk a bit about what responsive images are: an image is considered responsive if it retains its quality on varying device sizes without having an unpleasant impact on performance.
To better understand this concept, let’s take a look at some device dimensions:
Possible Full-Width Image Dimensions by Screen Sizes
- Large/X-Large commercial screens: 2000+ pixels
- Websites: 760 - 1200 pixels
- Mobile Phones: < 760 pixels
Let’s assume you have a mobile-first strategy for building responsive apps. You may decide to use 760px images throughout, without considering larger screens. If these images are meant to take the full width of the devices on which they are rendered, then your content will look distorted and unprofessional on websites or commercial screens.
Your next attempt would be to use the largest possible image (2000px) and scale it down based on the screen sizes on which it is displayed.
Down-Scaling Images
Using CSS or JavaScript to down-scale images only makes them dimensionally responsive. The following image illustrates this better:
Both on web and mobile devices, the size is still 8.9MB. Bearing in mind that your mobile phones have less resources than your PC, we still have more work to do.
Using only a down-scaling approach is not ideal because it does not account for the size of the image; just its dimensions.
We have already seen that up-scaling wouldn’t work either, hence we need something that handles both dimensions and size.
Size-Fitting
Our best option is to generate images based on the screen size and render them. This process can be extremely complex, but there’s a shortcut that can help you automate much of the process. You can make all images responsive in three easy steps with Cloudinary:
1. Include Cloudinary in Your Project
Add the Cloudinary SDK to your project simply by including it in your index.html using script tags:
<script
src="https://cdnjs.cloudflare.com/ajax/libs/cloudinary-core/2.3.0/cloudinary-core-shrinkwrap.min.js">
</script>
2. Add Images with data-src
You don’t want the images rendered immediately, until JavaScript runs. Hence, include the image using the data-src
attribute instead of src
:
<img
data-src="
http://res.cloudinary.com/christekh/image/upload/w_auto,c_scale/v1501761946/pexels-photo-457044_etqwsd.jpg
"
alt=""
class="cld-responsive" />
Using this approach, Cloudinary analyzes your browser screen first, resizes the image saved in Cloudinary storage as provided in data-src
, and then renders the image in the appropriate size and dimension using JavaScript.
Two things to note from the tag:
w_auto,c_scale
transformation parameters tell Cloudinary to dynamically generate an image URL scaled to the correct width value, based on the detected width actually available for the image in the containing element.- The class
cld-responsive
tells Cloudinary which images to apply this feature too.
3. JavaScript Call
Finally, initialize a Cloudinary instance in your JavaScript files and call the responsive
method on this instance:
const cl = cloudinary.Cloudinary.new({ cloud_name: 'YOUR_CLOUD_NAME' })
cl.responsive()
Remember to create a free Cloudinary account so you can receive a cloud name for configuring this instance.
This piece of code will walk through the DOM, find all image tags with the class cld-responsive
to apply size and dimension fitting images on them.
Final Words
Always keep in mind that when you use CSS like the following code below to make images responsive, it does not guarantee a good user experience:
img {
width: 100%;
height: auto;
}
The sizes of these images remain the same. Large images on mobile devices eat up resources (like allocated memory and running processes) causing slow downloads or unexpected behavior on the user’s device. Responsive images ensure that users save lots of data bandwidth & have great experiences when using your image-rich website or app.
Lastly, it’s good to keep in mind that the suggested approach relies on JavaScript. Therefore, the preloading capabilities provided by srcset
and sizes
are sacrificed and your browser must have JavaScript enabled for this feature to work.
Comments