Performance

How the Netflix TVUI team implemented a robust strategy to quickly and easily detect performance anomalies before they a

Each font variant (bold, medium, etc.) requires an additional file, which slows down navigation. Except if you use variable fonts!

Optimizing Core Web Vitals on The Economic Times website significantly improved the user experience and substantially reduced bounce rate across the entire website.

First load performance is important, but it's not everything. Users who load your site a second time will use their cache to get access to your content—so it's key to make sure it works well too, both for speed and correctness.

Missguided are one of the UK's most innovative and fast-moving fashion retailers but as with many other retailers, web performance hasn't always been our highest priority.

There's been an explosion in 3rd-Party Tags… And as Tim Kadlec once said

I’ve researched and learned enough about client-side memory leaks to know that most web developers aren’t worrying about them too much. If a web app leaks 5 MB on every interaction, but…

User experience vs. diagnostic metrics A few years ago, Google introduced the Core Web Vitals metrics. If you've been following web performance for a while, you know there are already a lot of metrics. Dozens and dozens of them, and new ones are being experimented with continually. So it's not surpr

Let’s look how to make the product page faster (& increase the conversion)

HTTP compression is an important part of the big web performance picture. We'll cover the history, the current state and the future of web compression. Lossless data compression makes things smaller Lossless data compression algorithms exploit statistical redundancy to represent data using fewer bit

HTTP/3 is here, and it’s a big deal for web performance. See just how much faster it makes websites!

See how people experience the speed of your website, then identify and fix performance issues.

12 tips to enforce control to secure Google Tag Manager (GTM) and prevent security or performance problems

A well-maintained, 10-year-old car will work fine to get you from A to B. A well-maintained bike will probably last even longer than the car. A 45-year-old landline phone can still receive and place calls. But what happens if you try to access a web page using a 3-year-old smartphone? How about a 5 or even a 10-year-old one?

Installation

Web performance report every week in your inbox.

Caching headers are surprisingly complex and often misconfigured. Here we look at some key cache scenarios and recommend the ideal headers to set.

Exif data can be a privacy threat if you upload images on the internet. Here's how to remove it in the Linux command line.

According to httparchive.org images represent about 43% of the page weight for the median desktop and mobile page. There are many things to consider with images such as using the proper type, serving the appropriate image for the device and situation (srcset or picture), and lossless or loss

When starting on a web performance journey, many companies’ first step is to start monitoring performance metrics over time. But the second step is often much harder - now that you have all of this data, what do you do when you see a regression? How do you sift through the clues to connect a change in a graph to the code that engineers ship to production? How do you become a performance detective? In this session, Katie will crack open her casefiles to share some real-world examples where performance metrics changed for the worse, and walk through how to find the culprit. You’ll learn what clues to look for to understand a regression in your Core Web Vitals, how different performance metrics influence each other, and when to use data gathered from real users vs. synthetic tests in the lab.

To serve users at the global P75 of devices and networks, we can now afford ~150KiB of HTML/CSS/fonts and ~300-350KiB of JavaScript (gzipped). This is a slight upgrade on last year's budgets, thanks to device and network improvements. Meanwhile, web developers continue to send more script than is reasonable for 80+% of the world's users, widening the gap between the haves and the have-nots. This is an ethical crisis for frontend. Meanwhile, the most popular tools and frameworks remain in stubborn denial, but reality is not moved by ignoring it: when digital is the default, slow is exclusionary.

We got to a point where we had the lightest chatbox on the market, with a compressed size of 232KB (full load), where other chatbox providers would often load up to a megabyte. Discover How!

Why your analytics shows your site as faster than it is, and why FCP is a key metric to optimise for.

View this on WebPageTest.org...

An extension for Chrome Recorder to export a recorder session as a WebPageTest Custom Script

Use the transform and opacity CSS properties as much as possible, and avoid anything that triggers layout or painting.