Cloudinary Blog

Are you guilty of making these mistakes when handling images on your website?

Most common image handline mistakes of web developers

Back in 2013, Cloudinary published a blog post entitled "Top 10 Mistakes in Handling Website Images". Though these top 10 mistakes still hold true, we've come up with a few additional points that we thought you'd find of interest.

As the number of images and videos on a website continue to grow, slower load times and thus a negative user experience are both growing concerns for any company.  An article this summer in The Fiscal Times, citing Internet data measurement company HTTP Archive, noted that the average website is now 2.1 MB in size, compared to 1.5 MB two years ago. And one of the biggest reasons for this growth is the addition of content such as videos and engaging images designed to drive more traffic to the site.  

The Fiscal Times - Web Slowing Down - Chart

The article illustrated that images account for almost 63 percent of the bytes (1,312 KB of the total 2,087 KB) of the average page by content type.  Video came in a distant second at 10 percent (208 KB).  

The impact of images on a website can be dramatic, eating costly bandwidth and increasing the time website visitors spend waiting for images to load. When every passing second reduces your website's overall conversion rate and ultimately revenues, it makes perfect sense to want to optimize your images and their delivery as much as possible.

If you're having problems, it's possible you're making one – or more – key mistakes with images, which prevent you from improving your website's performance and user experience. Here's a look at some of the most common mistakes, and how to avoid them:

Not using more efficient, modern image formats

Even though Google has added support for its WebP image format to Chrome browsers, and Microsoft has done the same for JPEG-XR in most of their Internet Explorer and Edge browsers, developers have still not embraced them.  Perhaps developers aren't aware of these formats, or maybe it's too difficult for them to deliver different image formats to various browsers and devices. As a result, they're sticking with the same JPG and PNG formats, and not taking advantage of how the modern formats can optimize their sites.

How to fix: Convert images to the WebP and JPEG-XR modern formats, while also adjusting compression quality to balance between the formats.  Also by detecting the specific browser that accesses each image and delivering a different version of the image to the respective browser, you can ensure users receive the best images possible, in terms of visual quality and file size optimization.

JPG Image
16.9KB JPG
WebP Automatic Image
6.9KB WebP

Embedding short video clips using the GIF format

Most developers rely on the GIF image format to display short video clips on news sites, media sites and social sharing sites. While the GIF format is easy to use for embedding video clips using a simple HTML image tag, it is not efficient for captured movies because the files are huge and slow to load, especially on mobile devices, resulting in high bandwidth costs and high CPU utilization.

How to fix:  There are several ways to deliver and embed the same clips and animations using modern file formats, such as Animated WebP for Chrome browser users.  Another approach is to apply lossy compression of the GIF File, which results in a slight visual quality reduction but significantly decreases the file size. GIF files can also be converted to MP4 or WebM video formats, embedding the clips and HTML5 video tags instead of the image tag. In most modern browsers, this works smoothly and the site looks exactly the same but loads much faster. By taking one of these steps, you will be able to reduce the file size dramatically, saving page load time, improving user experience and cutting bandwidth costs.

http://res.cloudinary.com/demo/image/upload/kitten_fighting.gif
6.3MB GIF
311KB MP4

Delivering 2X (Retina-display) images to all users

Modern mobile devices and laptops have high device pixel ratios (DPR). Because site owners and developers want their sites to look great on these devices, they embed double resolution images. While this is a good practice, many developers tend to deliver the same size images to all users. As a result, users with regular displays (e.g., non-Retina displays) must download the hi-res images while their displays only benefit from half the resolution. This results in wasted time waiting for pages to load and increases bandwidth costs unnecessarily.  

How to fix: Create different resolutions for each DPR value (e.g., regular images and double resolution images) and automatically detect the DPR value of the web page in the current user's browser. This will enable you to deliver regular images to users with regular displays and 2x resolution images to users with Retina display devices.

DPR 1.0 thumbnail in HTML

DPR 2.0 thumbnail in HTML

DPR 1.0 - 100x100 - 4.6KB                  DPR 2.0 - 200x200 - 12.1KB

And don't forget the top 10 mistakes highlighted in our previous blog post

  1. Wasteful browser-side resizing
  2. Unnecessarily high quality JPEGs
  3. Incorrect image file types
  4. Delivering non-optimized images
  5. Forgetting to strip image meta-data
  6. Delivering images straight from your servers
  7. Delivering static icons one by one
  8. Using images when CSS3 can be used
  9. Incorrect image cache settings
  10. Using a single image size across all delivery mediums

Want to correct these problems?

Do you find yourself making at least one – if not more – of these mistakes, and could benefit by re-evaluating your processes and optimizing the way you handle images?  

Cloudinary can help.  We've got you covered from upload through storage, manipulation, optimization and delivery. Sign up for free and discover how we can help you avoid these problems.

Recent Blog Posts

Build the Back-End For Your Own Instagram-style App with Cloudinary

Github Repo

Managing media files (processing, storage and manipulation) is one of the biggest challenges we encounter as practical developers. These challenges include:

A great service called Cloudinary can help us overcome many of these challenges. Together with Cloudinary, let's work on solutions to these challenges and hopefully have a simpler mental model towards media management.

Read more

Build A Miniflix in 10 Minutes

By Prosper Otemuyiwa
Build A Miniflix in 10 Minutes

Developers are constantly faced with challenges of building complex products every single day. And there are constraints on the time needed to build out the features of these products.

Engineering and Product managers want to beat deadlines for projects daily. CEOs want to roll out new products as fast as possible. Entrepreneurs need their MVPs like yesterday. With this in mind, what should developers do?

Read more

Your Web Image is Unnecessarily Bloated

By Christian Nwamba
Your Web Image is Unnecessarily Bloated

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:

Read more

Google For Nigeria: We saw it all…

By Christian Nwamba
Google For Nigeria: We saw it all…

Note from Cloudinary: Christian Nwamba, a frequent Cloudinary contributor, recently attended, and was a main speaker, at the Google Developer Group (GDG) Conference in Lagos, Nigeria. Christian led a session teaching more than 500 developers how to “Build Offline Apps for the Next Billion Users.” The stack he used included JS (Vue), Firebase, Service Workers and Cloudinary. Below is his account of the conference and his talk.

Read more
Viral Images: Securing Images and Video uploads to your systems

When was the last time you got paid $40,000 for a few days of work? That is what happened last year to Russian independent security researcher Andrey Leonov, who discovered that if you upload a specially constructed image file to Facebook, you can make Facebook's internal servers, nested deep within their firewalls, run arbitrary commands to expose sensitive internal files in a way that could easily lead to a data breach.

Read more