I wasted a day on CSS selector performance to make a website load 2ms faster | Trys Mudford
Picture me holding Trys back and telling him, “Leave it alone, mate, it’s not worth it!”
This just blew my mind! A fiendishly clever pattern that allows you to inline resources (like critical CSS) and cache that same content for later retrieval by a service worker.
Crazy clever!
Picture me holding Trys back and telling him, “Leave it alone, mate, it’s not worth it!”
The bar to overriding browser defaults should be way higher than it is.
Amen!
What Trys describes here mirrors my experience too—it really is worth occasionally taking a little time to catch the low-hanging fruit of your site’s web performance (and accessibility):
I’ve shaved nearly half a megabyte off the page size and improved the accessibility along the way. Not bad for an evening of tinkering.
This really is a disgusting exlusionary state of affairs.
I hate to be judgy, but I honestly wonder how the people behind some of these decisions can call themselves web developers.
A great talk from Addy on just how damaging client-side JavaScript can be to the user experience …and what you can do about it.
Browser are user agents, not developer agents.
A performance boost in Chrome.
A small-scale conspiracy theory from the innards of Google.
With this bookmarklet you’re only ever one click away from the Lighthouse results for a page.
Business, sustainability, and inclusivity.