How large DOM sizes affect interactivity, and what you can do about it
Large DOM sizes can be a factor in whether interactions are fast or not. Learn more about the relationship between DOM size and INP, and what you can do to reduce DOM size and other ways to limit rendering work when your page has lots of DOM elements.
Romuald Priol – Navigateur, metrics et outils – WLS 2021
La webPerf, c’est bien, mais en connaissant toutes les subtilités de la création de notre page c’est mieux \o/. Pendant 45 minutes, nous voyagerons à travers...
The impact of removing jQuery on our web performance
In this blog post, we explain the technical details of removing the jQuery library from GOV.UK’s public facing applications and the performance impact it had for our users.
Modern CSS rendering performance: The internals of web pages optimization In this talk, we demystify the browser’s rendering pipeline and explore the differe...
JavaScript SDK “Package Size is Massive” - So we reduced it by 29%
Developers started to notice just how big our JavaScript package was and yeah, we knew. We weren’t ignoring the issues; after all, we don’t want the Sentry package to be the cause of a slowdown. But to reduce our JavaScript SDK package size effectively we had to account for shipping new capabilities, like being able to manage the health of a release and performance monitoring, while maintaining a manageable bundle size. After all, new features == bigger package - usually.
5 Steps to Improve Website Performance Online Guide
There has never been a better time to deliver fast, resilient websites, but getting there demands an informed approach. So grab a hot beverage and let this guide illuminate the path forward.
Too often, any talk of web performance quickly ventures into the land of heavy geekery. Terms like DNS lookups, Gzipping, minifying, far future expires headers, caching, ETags and more are thrown around and consequently lose the attention of most non-techy people. This perpetuates a mentality that p
So often we cram a load of crap onto a single web page and then play silly buggers trying to get them to load efficiently. Instead design for actual performance.
Conversion of fonts to WOFF/WOFF2 and font subsetting with Glyphhanger · Florian Brinkmann
To use web fonts with wide browser support, we need the font files in and format. Who does not care about Internet Explorer, Safari on Mac OS before Sierra...
When It Comes to Good CX, Measurement Is Critical - GovLoop
Formalizing and distributing knowledge about CX is critical. However, there are a few elements of digital government that seem to have been overlooked.
Ever since responsive web design started, we've had a problem with the way images load on the web. Now, Firefox is fixing the problem. Add width & height att...
Don’t Sink Your Website With Third Parties — Smashing Magazine
In this article, Ken Harker explains what third-party resource requests really are and which common optimization strategies can help reduce the impact on the user experience. By carefully considering how third-party requests will fit into your website during the design stage, you’ll be able to avoid the most significant negative impacts.
Native apps often feature transitions between states that both look great and help communicate the type of navigation to the user. The bad news: creating tra...
I’ve been doing a few audits of late, and one thing that keeps coming up is the use of transition effects on page load (or above the fold content). This post looks at some of the performance pitfalls that can arise from this practice, as well as what you should keep in mind.
This post stems from a conversation I had with a good friend of mine last week. We were talking about how to boost website traffic, and conversions. As I explained to him, and as we'll get to in this post, there's more to the game than just fresh, keyword laden content.