Profile
The Man Who Keeps Rewriting the Rules of Fast
Scott Jehl doesn't chase headlines. He writes specification text and submits pull requests to browser engines. His name doesn't trend on social media. But the web moves faster because of him - literally. If you've ever loaded a responsive image in a browser, or had a stylesheet load without blocking your page, or watched a video that didn't needlessly fetch itself before you scrolled to it, you've benefited from Scott Jehl's work without knowing his name. That's the nature of his contribution: invisible infrastructure that makes the things you use every day less frustrating.
Today he works as a Senior Software Engineer on the Web Performance team at Squarespace in Brooklyn, New York. It's his latest stop on a 20-year journey through front-end development that has run through Filament Group, Catchpoint's WebPageTest team, and a stint advising on HTML Web Components with Begin. Before all of that, he spent roughly 15 years at Filament Group - an unusually long tenure in an industry that treats two-year stints as the norm. That loyalty tells you something about how he operates: he goes deep, not wide.
His work is characterized by an almost stubborn focus on the end user over the developer. Not the developer who has gigabit fiber. Not the developer whose MacBook Pro renders pages in 200 milliseconds on localhost. Scott thinks about the person on a 3G connection in rural America. Or in Southeast Asia, where slow and intermittent internet is a daily reality he observed firsthand during his travels there - and which reshaped his whole philosophy about what "good" means on the web.
"I realised that there are a lot of big problems still to be solved. The focus for me became performance, particularly on slow and intermittent connections."
His 2014 book, Responsible Responsive Design, published by A Book Apart, made the case that responsive design and performance weren't separate concerns. They were the same concern. You couldn't build something that worked on any screen and call it done if it loaded in ten seconds on a mobile network. Responsibility meant both. The book remains a landmark text in front-end thinking - concise, direct, and still relevant more than a decade after publication.
20+
Years Front-End
50+
Conference Talks
15
Yrs Filament Group
2
Books Published
Open Source
The Tools That Moved the Web Forward
Most front-end developers point to frameworks when asked what shaped the modern web. Scott Jehl points to problems. Each tool he built was a direct response to something that was broken or missing.
01
Respond.js
CSS3 media queries polyfill for IE 6-8+. Three kilobytes minified. One kilobyte gzipped. It let Internet Explorer users experience responsive design before their browser ever natively supported it. The responsive revolution didn't wait for Microsoft - Scott built the bridge.
02
Picturefill
The polyfill that made responsive images possible before browsers shipped the <picture> element and srcset attributes. It went through three major versions. It helped prove to browser makers that developers needed native support. They listened.
03
loadCSS
A tiny function that loads stylesheets asynchronously. It sounds small. The impact wasn't. It enabled a technique - inline critical CSS, async-load the rest - that can cut perceived load times in half. Scott's own words: "It can, in some circumstances, cut load times in half."
04
loadJS
The sibling to loadCSS. Asynchronous script loading, simplified. Small surface area, significant performance impact. Part of a pattern Scott refined over years: minimal code, maximum effect, no dependencies.
05
loading=lazy for video
Not a library. An official HTML standard. Scott led the effort to bring the loading="lazy" attribute to <video> and <audio> elements. Mozilla, Apple, and Chromium code owners all endorsed it. It became part of the HTML spec on March 23, 2026.
06
Web Platform Tests
Alongside the lazy media proposal, Scott contributed Web Platform Tests - the test suite that browser implementations must pass. It's not glamorous work. It's how you know a standard actually works across every engine.
The pattern is consistent. Scott doesn't build for developers who already have good tools. He builds for users who are being left behind. And then he moves the standard forward so the polyfill becomes unnecessary. The scaffolding disappears when the building stands.
Origin Story
The Connection That Changed Everything
There's a version of Scott Jehl's career that is purely technical: a CV of libraries, books, and conference appearances. That version misses the turning point. Traveling through Southeast Asia and experiencing slow, intermittent internet connections firsthand, Scott's focus shifted. Not toward better frameworks. Toward the actual experience of people on bad connections in places where fast internet isn't assumed.
"3G is still the most common connection speed in the US," he has said. "LTE hasn't dominated, even in cities." The implication is clear. If you're building for people on fiber, you're building for a minority. The web you build should work for the rest.
That perspective shapes everything. It's why he cares about lazy loading. It's why he wrote a book about responsible design rather than just responsive design. Responsibility isn't a moral stance - it's an engineering requirement. The web should be fast enough to be useful before you can say "Cumulative Layout Shift." If it isn't, usability doesn't enter the picture.
the moment it clicked
He spent 15 years at Filament Group putting that philosophy into practice. In an industry where two years at a company qualifies as tenure, fifteen years at one place is practically unheard of. It's the kind of commitment that comes from actually believing in the work, not just the resume line.
Standards Work
The Long Road to loading="lazy" on Video
In December 2025, Scott Jehl and a team at Squarespace - including colleagues Credo Duarte, Brad Frost, and Zach Lysobey - submitted a proposal to the WHATWG: add the loading="lazy" attribute to HTML <video> and <audio> elements. Images had supported lazy loading for years. Media elements didn't. Every video on a page, regardless of whether a user ever scrolled to it, initiated a network request.
The proposal required something rare in browser standards work: simultaneous buy-in from the code owners at Mozilla, Apple, and Chromium. These are three organizations with different philosophies, different shipping timelines, and different processes. Getting all three to endorse a change to the HTML specification takes evidence, patience, and persistence. Scott brought all three.
He contributed Web Platform Tests to validate the behavior. He worked with Firefox and WebKit teams on browser implementation patches. He tracked the WHATWG review process through its formal stages. On March 23, 2026, it became an official web standard.
"Performance should guide every design decision, not something that bleeds into the coding process itself."
The announcement on the Squarespace engineering blog was characteristically understated - a detailed technical walkthrough of how the standard came together, not a victory lap. That's the Scott Jehl style. The win is in the spec, not the announcement.
Speaking & Teaching
From Stage to Screen: Teaching a Generation of Developers
Scott has delivered more than 50 talks and workshops at major international conferences. Ten of those have been at An Event Apart - one of the most respected front-end conferences in the industry. He has appeared at SmashingConf, Performance.Now(), Fronteers, Web Directions, Mobilism, CSSConf, beyond tellerrand, and dozens more.
At SmashingConf New York 2024, he appeared as a mystery speaker - the name withheld from the program until the last moment. His talk: "Web Components Can't Save Us. But You Can." The title alone is a thesis statement. The technology doesn't rescue you. The craft does. The thinking does. The care does.
Beyond live events, Scott has built online courses. His 2024 course, Web Components Demystified, went deep on a technology that the industry has spent years arguing about. His earlier Lightning-Fast Web Performance series brought his conference workshop material to developers who couldn't get to the conference. The format suits him - dense, precise, practical, with no padding.
Achievements
The Highlights Reel
01
HTML standard contributor - lazy loading for video and audio, adopted March 2026 with endorsement from Mozilla, Apple, and Chromium
02
Author of Responsible Responsive Design (A Book Apart, 2014) - a landmark text in front-end performance thinking
03
Co-author of Designing with Progressive Enhancement (Peachpit/New Riders, 2010) - one of the first books to codify the progressive enhancement philosophy
04
Creator of Respond.js, Picturefill, loadCSS, and loadJS - tools that shaped how the web adopted responsive design and performance patterns
05
50+ international conference talks including 10 appearances at An Event Apart, plus SmashingConf, Performance.Now(), Fronteers, and more
06
Contributed Web Platform Tests for new HTML standards - the test suite browser engines must pass to ship compliant implementations
Philosophy
Performance Is Not a Feature. It's the Floor.
Scott Jehl has been saying this for years, in different words: performance isn't something you add to a website. It's the baseline below which nothing else matters. A slow website doesn't get to be judged on its UX, its design, its content. It gets abandoned before any of that is relevant.
That conviction runs through everything he builds, writes, and teaches. The responsible in Responsible Responsive Design isn't rhetorical. It means something. Every design decision has a performance cost. Every added script, every large image, every blocking stylesheet - these aren't neutral choices. They're choices that affect real people on real connections in real places.
His approach to web standards work follows the same logic. Polyfills are temporary scaffolding. The goal is always to move the behavior into the platform itself, where it works for everyone without requiring developers to know about it. Respond.js solved a problem until browsers solved it. Picturefill solved a problem until browsers solved it. Now loadCSS patterns are being absorbed into how browsers handle CSS. And lazy loading for video and audio is in the HTML spec.
The scaffolding disappears. The building stands.
web-performance
progressive-enhancement
responsive-design
web-standards
accessibility
web-components
html
css
javascript
open-source
whatwg
squarespace
filament-group
webpagetest
a-book-apart
smashingconf
an-event-apart
Timeline
The Long Game
2010
Co-authored Designing with Progressive Enhancement with Peachpit/New Riders - one of the first books to rigorously define the PE methodology
2012
Released Respond.js - CSS3 media queries polyfill for IE 6-8+, 3kb minified, 1kb gzipped
2013
Created Picturefill, the responsive images polyfill for the <picture> element and srcset
2014
Published Responsible Responsive Design with A Book Apart. Released loadCSS for async stylesheet loading
~2007-2022
Senior Interactive Designer at Filament Group - approximately 15 years building accessible, performant web applications
2022-2023
Senior Experience Engineer at Catchpoint / WebPageTest - led design of WebPageTest Pro Experiments and Carbon Control
2023
Web standards consulting with Begin, focusing on HTML Web Components and the Enhance framework
2024
Joined Squarespace as Senior Software Engineer, Web Performance Team (June). Launched Web Components Demystified course. Mystery speaker at SmashingConf New York
2026
loading="lazy" for HTML video and audio becomes an official web standard (March 23) - a proposal Scott led from Squarespace with cross-browser endorsement