For government, GOV.UK is often the only place a user can get information. If the website were to perform badly, we become a single point of failure.
Great rundown of why performance is so important to GOV.UK and how the context of their visitors can vary dramatically, even within the same city.
In this post, we’ll look at the new loading attribute which brings native <img> and <iframe> lazy-loading to the web!
Exciting to finally see this ship! Folks have been asking for a standards-based way to support lazy-loading images for years.
Gives me hope that maybe, someday, we’ll have element queries.
When we’re evaluating technologies for appropriateness, I hope that we will do so through the lens of what’s best for users, not what we feel compelled to use based on a gnawing sense of irrelevancy driven by the perceived popularity of newer technologies.
I always like seeing how other folks handle performance audits. Here, Jake walks through 10 F1 sites, auditing them primarily with WebpageTest and a smattering of Chrome Dev Tools.
Academic background or not, technical education doesn’t stop once you get a job. On the contrary: nothing in tech stays in one place, and the single most valuable skill you can possess to remain employable over time is learning how to learn.
Some great advice here from Sarah on learning.
Handy little reference from Addy Osmani showing how Chrome handles JavaScript scheduling.
I’ve being using preload with clients over the last few years but I have never been completely satisfied with the results. I’ve also seen some things I hadn’t quite expected in page load waterfalls so decided to dig deeper.
Excellent work digging deeper into preload by Mr. Davies.
Ten years ago the network was the main bottleneck. Today, the main bottleneck is JavaScript.
A very approachable explanation from Sarah about what Hooks are and the problems they solve for Vue.
Ooo…this is smart. Ire explains why you should use the :lang pseudo-class instead of the [lang=''] attribute selector.