18 May, 2017 (updated 19 May, 2017)
I read and write often about web performance. As time has gone on, I've found myself less drawn to the technical aspects of the issue — the human side of web performance proves far more intriguing. I'm interested in how our actions as designers and developers makes life easier for users. Performance is a vital part of the user experience. Those who appreciate its importance aren't simply improving performance metrics, they're improving users' lives. I find my work most rewarding when I know I've built a site that's fast, or if I've remedied performance problems on ailing sites. To me, that's the good fight, and I sleep best when I've fought it.Read More »
In that fight, the adversary of performance is the lay of the land between the server and the browser. It's an adversary we can't vanquish. We can only diminish its effects through sound design and architectural decisions. Unlike villains in familiar stories, the journey of data between the server and the browser is not often a sentient adversary. It's a coldly neutral foe. At least, that's generally how it's been for web designers and developers in The United States.
We went through one of the most bizarre election seasons last year, the outcome of which became a harbinger for many harsh realities that may yet come to pass —one of which is that net neutrality may very well cease to exist. No matter where your beliefs fall in the political spectrum, the death of net neutrality will impact you as a practitioner of the web, and not for the better.
As a content platform, the web is as small-d democratic as it gets. If you have an idea for something, you can build it and put it on the web, no matter how gravely serious or silly it may be. The only barriers to entry are time and money. Most importantly, the speed at which users access content is unencumbered by anything other than the lay of the land between them and whatever server that content is hosted on. For all of the problems in this country, we have at least treated the internet as an essential vehicle for free expression. Abuses have certainly occurred, but without net neutrality, those abuses will no longer be considered unlawful. They'll become a common feature of the landscape that we'll have to cope with.
This administration's FCC has already begun dismantling Title II rules that protect net neutrality. They want to make the web a platform where internet service providers hold unilateral authority to decide which content providers should be prioritized over others. This move will undoubtedly be framed by net neutrality opponents as a massive new opportunity for investors to further profit from industry deregulation. Investor opportunity does not necessarily translate to a benefit for users at large.
When we discuss performance in developer circles, we often use the phrase "performance matters!" Performance matters because users matter. Performance matters because fast sites are better conveyances for ideas than sluggish ones. If net neutrality is watered down or killed off altogether, performance will matter more than ever. Performance best practices may well be the only tools you'll have to overcome capricious network throttling on the part of service providers, particularly if you can't afford to have your content prioritized over competitors with deeper pockets.
If you're a performance-minded developer, you're likely already well-equipped, and continuing education is your plan going forward. But what if you don't know much about this vital topic? You've got some catching up to do:
High Performance Web Sites
This is a seminal text by Steve Souders, one of the foremost experts on the topic. If you know nothing about web performance, consider this book your starting point. Despite being almost ten years old, it's still largely relevant today.
Designing for Performance
Authored by Lara Hogan, Designing for Performance is clearly written in approachable language that not only covers technical topics, but also cultural and soft skills-related challenges as they relate to the problem of performance. It is, above all, a pragmatic guide for performance-focused web developers, and richly deserves space on your shelf.
High Performance Browser Networking
Few in this industry can boast of Ilya Grigorik's technical acumen, and High Performance Browser Networking proves it. This book doesn't just give you tips for improving performance, it goes deep into its technical underpinnings. If you've ever wanted to understand how network architecture affects site speed, this is your book.
Beyond the titans, there are also a wealth of bloggers out there who fight the good fight for users every day. Compared to these people, I'm a Johnny-come-lately to the topic, but I've written a book of my own. It's up to all of us to get educated on this subject, because if net neutrality falls, the day will come where performance isn't a matter of optimization, but a survival strategy.
Net neutrality's fate is uncertain, but not sealed. Voice your opposition to the FCC. Contact your representatives and senators. Keep the pressure on. It could pay off. If it doesn't?
Then you better knuckle down and focus on speed.
Thanks to Susanna Kline for editing this piece.