jQuery.lazyLoader, Semantic, organic responsive images?


I’m often a bit of a purist, but as I age, I’m realising more and more the history of the web, much like most other histories is a pretty messy pit of layers laid on top of layers. After reading this revolutionary email from the birth of the img tag, I’m reminded we’re just working on the next layer so it’s probably going to be messy ;).

I have been reading this evening over people’s thoughts about how we tackle responsible responsive images and there seems to be no perfect method. In fact many of the methods currently being seen have major gotchas. It just feels like we are far from getting a stable way of providing responsive images using the img tag.

There have been a few interesting discussions about how this could play out in the future but like a lot of people I want to have a go at doing something NOW! So taking the pragmatic view that done is better than perfect I have developed a simple tool to add to many other options out there which fitted well for what I was trying to achieve.

The essense of the idea

The essence of this idea is that if the image being used is an essential part of the content then it needs to be discoverable BUT does it really need to be represented by an img tag? Instead could it be linked to like most other content? That would then eleviate the need for all this hackery and achieve the following:

  • A discoverable bit of content
  • The ability to reference find and crawl the source organically
  • The ability to enhance this piece of content depending on many device factors
  • No loading a small and a large image in desktop environments
  • The potential to not serve an image at all in environments which are completely text based

But I have found these areas to be tricky:

  • When needing the piece of content to be a link itself (you can’t nest links)

What does it look like?


With the following markup

<div id="#lazy">
    <a href="myimage.jpg">my image</a>

You run the plugin on the links

$('#lazy a').lazyLoader();


<a href="myimage.jpg">my image</a>

converts to

<img src="myimage.jpg" alt="my image" />

and with data attribute:

<a href="mypage.html" data-img="myimage.jpg">my image</a>

converts to

<img src="myimage.jpg" alt="my image" />

Responsive images

If you want to dynamically load images dependent on the screen dimensions then you can use the following.

<a href="myimage.jpg"
>my image</a>


    steps: [768,990] // this must be sorted correctly

Or it also supports dynamic urls so you don’t need all those data attributes.

<a href="myimage.jpg">my image</a>


    img: function(url, windowWidth) {
        if (windowWidth >= 768){
            return url.replace(/.(jpg|gif|png)$/i, '-mega.$1');
        } else {
            return url;
    steps: [768,990]

This function appends “-mega” on to the end of the url if the windowWidth is greater than or equal to 768.

<img src="myimage-mega.jpg" alt="my image" />

To Conclude

Now I’m very sure that there are people who are far more intelectual than me that will pick this to pieces. Well.. I’m interested in how this sits with them. It’s certainly going to be field tested and I wonder how my view on it will evolve as I put it to the test. I just thought this might a) be the right tool for a niche b) spark some thoughts outside the common paths which are being followed.

View a demo, View the source

Work with me

Dave is a cohesive team member, widely popular with his colleagues and always inspiring quality, exploration and innovation. One of the true ‘greats’ we’ve had the pleasure to work with

I believe in community, in inspiration and creativity. I believe it's an inspired team and a laser focus on the user's experiece that will produce the best results. I want to help frontend teams live inspired, be productive and scale better.