Mo’ Pixels Mo’ Problems

by Dave Rupert

29 Reader Comments

Back to the Article
  1. “Above all: use your brain”. Love it!

    It’s interesting that in nearly every other facet of our industry we’re pushing for device/context agnostic solutions but with images, we going the other direction. Damn pixels!

    I’ve been using SymbolSet for icons and it’s a brilliant solution.

    Copy & paste the code below to embed this comment.
  2. Nice overview Dave, thank you.

    Loving the emphasis on Progressive Enhancement and general common sense :) I too feel that people jump on JS solutions a bit too quickly.

    You touch on this but it might be worth pointing out that creating `@2x`images does _not_ result in images that are 4x the filesize. Image compression is smarter than that.

    Re: bitmap images you already mention your `1.5x` trick but you do not mention another simple and common sense approach that shaves off even more of the filesize: simply reducing the image _quality_.

    Thomas Fuch’s has written great little blog post on this:

    E.g. one can simply create a JPG image that is about 1.5-2x as large as commonly needed and _reduce the image quality drastically_ (from say `60` to `30`). Then you _scale the image down in your HTML_.

    Because ‘retina’ screens have such high density the JPG artifacts are barely visible and the filesize will remain quite small because of the reduced quality/compression.

    YMMV, of course, so it should be tested but it might be another simple client-side solution for some (most?) bitmap images.

    I am not completely sure I agree with your statement _"We need a purely front-end solution to high resolution images.“_

    What do you think of services such as or RESS in general?

    Copy & paste the code below to embed this comment.
  3. I tried to use icon sets in my most recent project, but the page load slowed significantly, to the point that there is always a visible jink in the page as the icon loads on test systems (in all browser tested: IE9/Chrome/FF).

    Using images seemed to be a better solution as they loaded instantly.

    Obviously I did not have the advantage of a truly scalable solution, but as I was using few icons the bandwidth requirements were similar and the performance of the page was far more important than minor artifacts on hi-res screens.

    Copy & paste the code below to embed this comment.
  4. @davidhund You’re exactly right. Image compression gets pretty great and it’s truly not linear. But that greatly depends on the type of image. I tried a variety of scenarios (Obama, Ronald Reagan, A cat, etc) and doubling the resolution, usually sat in the 300%+ range.

    I suppose that statement could be massaged over time with more data.  That would be an interesting test case to build.

    re: Quality - I’ve heard musings of the “Quality Hack” that you described for serving images, but haven’t seen a blog post or demo outlying that. I’d be hesitant to give anyone a Quality: 30 graphic, but I bet it totally depends on the situation.  You should write a blog post on that and teach the world, please!

    I like ReSRC and Sencha.IO, but I’m hesitant to use anything that doesn’t document it’s targeting strategy (is it UA sniffing? Setting a cookie or something?). When targeting fails, it fails really bad (see Basecamp Mobile, etc). Additionally, I’m hesitant to use a 3rd party service (beyond a CDN) for something as simple as images. That said, I think a lot about dedicated “media boxes” might become a part of the frontend web stack in the future, due to the increasing complexity there.

    Copy & paste the code below to embed this comment.
  5. I quite like the “use your brain” aspect of the article. Too many times, too many people simply use the “whatever other people use” method without understanding the impact(s) elsewhere.

    I would like to have read though that the picturefill you’re refering to in the article, that you’ve started using, does infact *require* javascript to function properly.
    Absolutely there are no server techniques required in it’s usage but it seems a bit misleading advocating this technique without at least mentioning it requires it’s usage, especially with the JS paragraph at the beginning of them article.


    Copy & paste the code below to embed this comment.
  6. @pitchfordD Good point. I should have made that more clear.

    Worth noting: Picturefill goes to great lengths to have a proper no-JS fallback, it’s truly a progressive enhancement. Also, the goal of Picturefill is to actually “proto-fill” (maybe not a word) the Picture element as if it existed in HTML today. I’d love to not use JS to poly/proto-fill this problem.

    Copy & paste the code below to embed this comment.
  7. @Dave Rupert Re: the Quality trick: I assume you’ve taken a look at that Thomas Fuchs blog post? He links to a (minimal) example. @pornelski (of ImageOptim fame) also mentions the technique:

    You are completely right though: this needs more testing and lowering the quality for supersized bitmap images might not be appropriate in all scenario’s.

    Good points re:server-side services. Wondering what you have in mind when you speak of ‘media boxes’. Many CMS’s already have some built-in (Just In Time) image scaling etc. so building a ‘_personal CDN_’ could be a possibility…

    Copy & paste the code below to embed this comment.
  8. Unfortunately for everyone involved with SVG and vector graphics, Illustrator’s output in this format is terribly unoptimized. For one thing, it insists on using _3 decimal spaces_ for every coordinate number, while most images would look great with _2 significant digits_. That would be a significant saving itself.

    Fixing this would take a bit of work. Luckily, for most images using SVG Cleaner——is more than enough. Perhaps with more interest and activity SVG tools will be improved further. For example, there is no tool in existence that would make it easy to make simple SVG animations without resorting to programming them by hand.

    Copy & paste the code below to embed this comment.
  9. @luminarious If you can make and popularize an SVG tool like that, you can have some of my money. If you open source it, you’ll have my respect forever.

    Considering that 99% of all SVGs used on the web will be exported directly from Illustrator, it’d be great to have that problem solved soon. There are lots of smart people at Adobe, so perhaps lobbying for a “simplified version” on export in Illustrator would be a net win for the internet. Or, you could build that SVG-Smush tool then get acquired by Adobe and then be a millionaire! We all win.

    Copy & paste the code below to embed this comment.
  10. how does picturefill address the bandwidth issue?

    Copy & paste the code below to embed this comment.
  11. @pauldewouters Picturefill doesn’t address bandwidth, but it its current state the Picture element would hand over 1x/2x determination to the browser via @srcset. Hope that makes sense.

    Copy & paste the code below to embed this comment.
  12. Pretty damn useful. I have been to looking for something that tackled this issue.

    Only nitpick I have is that the script should check to see if the src attribute matched the data-src before it set the value. I had Firebug open as I was resizing the browser and saw a lot of useless requests.

    Copy & paste the code below to embed this comment.
  13. My experience with SVG is that it’s not as rosy and well-supported as most of these kinds of articles make out.

    Want your SVG to be flexible in a responsive design? You will run into sizing problems in iOS Safari.

    Want to make your SVG a clickable link? The most reliable way is to absolutely position an anchor tag over it - which is not the most semantic.

    Want to use an SVG background with “background-size: cover”? Want to use an SVG as a border-image? Browsers handle these very inconsistently, if at all.

    In my opinion, these bugs are the reason that SVG isn’t more widely used, not web developers unwillingness to use it.

    Copy & paste the code below to embed this comment.
  14. Dave - Regarding SVG exports from Illustrator, I’ve always done a 2-step process:

    First, simplify the artwork in Illustrator as much as possible, that means un-grouping, merging shapes, removing extra points, etc.  Time consuming depending on the graphic, but worth it.

    THEN you can do an SVG export, but be sure to open it up in a text editor and do another cleanup pass for anything that looks strange.

    Copy & paste the code below to embed this comment.
  15. It’s a nice article, but I feel it doesn’t deal with the issue that was actually questioned in the first place…that of people with devices that are out of sync with their environment’s bandwidth. We can’t focus on front-end solutions if we ignore that someone may have a large device on a small network speed, or a small device on a high speed WiFi.

    “I have written more about it here.”:

    Copy & paste the code below to embed this comment.
  16. I’m curious, I downloaded the jpg’s from the POTUS example and they’re all set to 300 DPI and not 72 DPI. 

    I’m curious if there’s a reasoning behind that?

    Copy & paste the code below to embed this comment.
  17. What are your feelings about this technique? “Adaptive Images by Matt Wilcox”:

    From what I see, it has a significant PRO of being able to work on existing sites without having to change any markup. So this could be used to upgrade existing sites without having to spend a lot of time working on them. Also, you only have to have one version of the image and the script takes care of the multiple sizes for you.

    The CONs of course are that it requires PHP and uses the server fairly heavily. I’m not sure how this would impact page load times. But it sounds like a very interesting solution.

    Copy & paste the code below to embed this comment.
  18. Fantastic assessment of the current situation and some useful avenues to explore.

    As an aside, if you run that threeamigos.png image through ImageOptim (a handy OS X wrapper for PNGOUT, OptiPNG and AdvPNG to losslessly brute force PNG filesize down) it saves another 10KB and comes down to 74KB.

    Copy & paste the code below to embed this comment.
  19. @skeg64 SVG is trickier than it seems. But basic, “no-frills” embedding is more-or-less supported across modern browsers. But you should totally write a blog post with a support chart, or put it out on a site somewhere, submit it to

    @splatcollision You should blog about that! The internet needs more education, less Top 5 posts. I think the “Art of Massage and SVG” would be a great blog post title! :)

    @John Bertucci That’s due to the source (TIFF) file’s resolution. I wanted to work with totally uncompressed images as a source just to eliminate the resolution variable there. If I can find time, I’ll do 72ppi versions and see what the difference there is.

    @ryangiglio I like Adaptive Images, I totally do. And for existing sites, like you mentioned, with years of content behind it (like Chris Coyier’s CSS-Tricks), I think it’s a great solution. I’ve heard *the following is hearsay* that there are CDN issues with that, which won’t work for high-scale sites. That said, Matt Wilcox is a smart guy and very involved in the RWDimages process.

    @jaikdean Bonus savings!

    Copy & paste the code below to embed this comment.
  20. Hey Dave,

    Although I agree with most of the article, the ‘three amigos’ example SVG you posted is rather misleading and as @luminarious and @splatcollision pointed out far from what it could be.

    You see, what you guys did is take whatever .ai you had and export it from Illustrator as is. Also because the source was rather poluted with dozens of overlapping paths and points the output ended up being huge as well.

    I’ve been spending rather painful amounts of time recently diving into SVG optimisation and here’s what I learnt:

    1. merge your shapes and make as many compound masks as you can to reduce the amount of SVG tags.
    2. before saving: Object > Path > Simplify (even @ 99 precision you can kill a lot of points)
    3. when saving, reduce decimal points from 3 to 1.
    4! Reuse, reuse, reuse. Learn your SVG before you start using it. Just by cloning and transforming your corner shapes rather than redrawing them, I went down to 290KB. Now if you do the same for some other shapes—e.g. those circular frames— you can drop another chunk of redundant data.
    5. Optimise output by removing unnecessary garbage, tags, whitespace, styles, etc.
    6. Minify.
    7. Always serve it gzipped - either automatically or manually as .svgz file.

    To prove these points - here’s a very rough optimisation result I achieved mostly with regex and Illustrator automation, hence few bits and pieces may differ: When you serve it gzipped it’s only 72KB. If You reorganised the whole file I imagine you could easily get down to 50KB.

    I hope that helps anyone who wants do dive into SVGs.

    Copy & paste the code below to embed this comment.
  21. I started my site when I was in Nepal, so I had no choice but to use extremely small file sizes, as anything else would take too long to upload and the internet connection would cut out before it finished. Now that I’m back in Europe, I’ve actually continued using only small-sized and highly compressed photos, mainly out of a realization that many people the world over would never get to see most of the photos were they too large.

    I wouldn’t mind having larger images though, so I’ll have to try a few of your workarounds and see if they work for me.

    Copy & paste the code below to embed this comment.
  22. Hi Dave,

    Umm.. I have a JavaScript solution that really does prevent the image from downloading prior to selection, and it let’s you use the picture elements (or img srcset syntax) without the need for div’s etc (although it does require noscript).

    Just thought you’d like to know..

    It does have a few dirty little secrets, but if you want to avoid the double download, you gotta do what you gotta do.

    Best regards,


    p.s. it’s a work in progress, but it does work across all modern browsers

    Copy & paste the code below to embed this comment.
  23. SVG has been an awful long time in coming and, while I’m very much in favour of it and have been using it in web-based stuff since about 2006 I can tell you that it is far from optimised. Performance in most browsers apart from Opera was dreadful until a few years ago and you need either plugins or compatibility libraries (Raphael et al.) for Internet Explorer which I think is only adding support with version 10. Printing was often almost impossible. Also, as it’s XML-based it’s inherently inefficient - I’d love to see a JSON version which would be both smaller and faster to parse. Support of the format between authoring tools is also terrible. Try working with the same file in say Illustrator, Omnigraffle, Inkscape and DrawPlus. Nevertheless, it really is the bees knees for logos, claims, etc. and can’t be beaten for anything that gets printed - this is the big lacuna in your article: almost everything you say also applies to print media.

    But I hate all the front-end only kludges for dealing with different pixel-densities. Backend-support preferably in the file-formats is essential. The “prefetching” behaviour of browsers could easily be modified by the browser makers or even put in the users’ hands. If you want small bitmaps of great quality - take a look at webp. I think mod_pagespeed now supports it if the browser does. It’s the best diet you can put your photos on.

    Copy & paste the code below to embed this comment.
  24. re 12:41 pm on September 25, 2012 by Dave Rupert

    Dave, I wonder if 99% of SVGs are exported from Illustrator as that format is quite popular with wikipedia nowadays, so whenever, say a blogger or private website owner, uses their pictures,  chances are it’s a SVG, as this is handy because of the license, mostly creative commons. Private owners should outnumber web designers by far and most of wikipedia’s SVGs should be creations of open source software.

    Copy & paste the code below to embed this comment.
  25. I like your SVG suggestion. I think it provides the simplest solution.

    Copy & paste the code below to embed this comment.
  26. You’re SVG threeamigos.svg isn’t 400kb, but 140kb.

    It can be served compressed like html, it’s xml after all, or even better, pre-compressed as svgz.

    Copy & paste the code below to embed this comment.
  27. Oh Lordie… Everything i knew was wrong))))
    The more i learn - the more i see i know nothing)

    Copy & paste the code below to embed this comment.
  28. You nailed it. I live overseas and pay a FORTUNE for bandwidth.

    Copy & paste the code below to embed this comment.
  29. What’s the difference between using the symbol packs at $29 to $50 versus free text symbols with an individual css for the font style (eg Hebrew David, or Times New Roman Latin 1)? Looks like a lot of expense for something a stunned bunny can do for free- if you have the pack you can just type in them, or what? The sites don’t explain.

    Copy & paste the code below to embed this comment.
  30. Sorry, commenting is closed on this article.