Author

A photograph of Jeremy Wagner. He is standing against a backdrop of grass and trees, with a green-to-blue swash on the left side of his hair.

Jeremy Wagner

Jeremy Wagner is more of a writer than a web developer, but he does both anyway. On top of writing Responsible JavaScript and making websites for longer than he thought probable, he has written for A List Apart, CSS-Tricks, and Smashing Magazine. Jeremy will someday relocate to the remote wilderness where sand has not yet been taught to think. Until then, he continues to reside in Minnesota’s Twin Cities with his wife and stepdaughters, bemoaning the existence of strip malls.

Also from this author

Now THAT’S What I Call Service Worker!

If you’re looking to achieve the single-page app level performance without the overhead (and boot time) of a huge JavaScript library or having to completely rewrite your website in a new technology, Jeremy Wagner shares a clever approach combining Service Worker and streamed web page partials you’re sure to love.

Responsible JavaScript: Part III

Convenience always comes at a price. On the web, developer convenience often means third-party JavaScript—and we pass the hefty cost on to our users. Jeremy Wagner shows us how to get and keep third-party scripts under control through clean-up sprints and eternal vigilance in Part III of Responsible JavaScript.

Responsible JavaScript: Part II

Web development is hard. We don’t always get it right on the first try. Fortunately, we don’t have to get everything perfect from the start. Jeremy Wagner provides some helpful ways to start recovering from our collective JavaScript hangover.

Responsible JavaScript: Part I

The web is drowning in a sea of JavaScript, awash with unnecessary bloat, inaccessible cruft, and unsustainable patterns. Jeremy Wagner plots a course to navigate the JavaScript Sea responsibly by building the right things the right way and using the web platform the way it was meant to be used.

Designing for Research

Image quality may be about striking the balance between speed and quality, but there's more to it than meets the eye. What if, despite having methods to develop better and better image experiences for the web, the user disagrees? In a quest to find answers, Jeremy Wagner takes us through an image quality study that he designs, develops, and iterates on with user feedback. Asking "Why?" is no easy undertaking in research. His lossy is your gain.

How People Perceive Lossy Image Quality: A Study

If beauty is in the eye of the beholder, the same can definitely be said for the ugliness of those "jaggies" we often see in compressed images. Our own Jeremy Wagner is on a mission to quantify image quality as it relates to performance. Can you help him out?

Using HTTP/2 Responsibly: Adapting for Users

Depending on your audience’s capabilities, a site optimized for HTTP/2 may be detrimental for a segment of your users. Jeremy Wagner shows us how adaptive content delivery can improve site performance caused by incompatible browsers.

Considering How We Use HTTP/2

HTTP/2 is a rough experience on incompatible browsers. Jeremy Wagner explains the true extent of real-world performance problems, and how to adapt delivery of site assets to a user’s connection.