Website Speed Test
Here’s a handy free tool from Calibre that’ll give your website a performance assessment.
A handy little for calculating your performance budget based on how long you want your page to take to load on a particular connection.
Here’s a handy free tool from Calibre that’ll give your website a performance assessment.
One dev team made the shift from React’s “overwhelming VDOM” to modern DOM APIs. They immediately saw speed and interaction improvements.
Yay! But:
…finding developers who know vanilla JavaScript and not just the frameworks was an “unexpected difficulty.”
Boo!
Also, if you have a similar story to tell about going cold turkey on React, you should share it with Richard:
If you or your company has also transitioned away from React and into a more web-native, HTML-first approach, please tag me on Mastodon or Threads. We’d love to share further case studies of these modern, dare I say post-React, approaches.
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.
Safari 18 supports `content-visibility: auto` …but there’s a very niche little bug in the implementation.
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.
Improving performance with containment.