Jeremy Keith recaps Scott’s An Event Apart, Seattle presentation where Scott runs through web performance best practices.
The Bottleneck of the Web
It’s not just javascript. Images certainly contribute to bloat. But the slowness I see on most sites I benchmark is due to excessive (and often unnecessary) javascript.
Web Accessibility and Autism
Rakesh Paladugula:
Web is for all, people experiencing autism are part of this user base. How can you make sure that your digital content can be made comfortable for these set of users?
Best practices all around.
It’s Not About the Device.
Ethan Marcotte’s thoughts on viewing the web on a watch, and why the terms “mobile,” “tablet,” and “desktop” should generally be avoided when designing for the web.
A Netflix Web Performance Case Study
Addy Osmani discusses how the Netflix team decreased Loading and Time-to-Interactive by 50%, and reduced their JavaScript bundle size by 200kB on the Netflix logged-out homepage.
HighEdWeb 2018
My presentation for HighEdWeb 2018 in Sacramento was about our latest redesign of www.nd.edu and the performance goals we set for ourselves and how we tried to achieve them.
Lighthouse 100
We would have had a perfect Lighthouse score if the tool didn’t assume our Google fonts would be invisible while webfonts are loading.

Users may get a bit of FOUT, but the text uses a fallback until Google Fonts finishes loading. So I’m going to go ahead and call it a perfect 100.
Be Better: Accessibility
Everything is broken. And it’s broken because we broke it.
Accessibility isn’t something we should do because we might get sued. It’s something we do because it’s right.
Building a University Website
The current version of www.nd.edu was launched on April 1, 2012. While the site has served us well for six years, it’s time for a refresh. For the past several months, ND Strategic Content, the ND Web Team, and many partners across campus have been working together to create something fresh and new.
Chrome 68 Marking "http" as "Not Secure"
Starting with version 68 (arriving July 2018), all non-https sites will be marked as “Not secure” by Chrome. If you’ve been putting off making the switch to https, now’s the time.