Erik Runyon

Jeremy Keith recaps Scott’s An Event Apart, Seattle presentation where Scott runs through web performance best practices.

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.

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.

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.

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.

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.

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.

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.