"Managing your service worker cache invalidation is a key step in making your progressive web app a rich robust experience. It ensures that the content your customer sees and interacts with is the freshest content possible. It also guards your app from overstepping the cache quota and potentially causing a complete purge of everything you stored."

"This post will perform an honest audit of the entire “cost” of Boomerang on a page that it is measuring. We will review every aspect of Boomerang’s lifecycle, starting with the loader snippet through sending a beacon, and beyond. At each phase, we will try to quantify any overhead (JavaScript, network, etc) it causes. The goal is to be open and transparent about the work Boomerang has to do when measuring the user’s experience."

The next time you get something done with DevTools, ask yourself if it makes sense to automate it, and how much time this will save down-the-line.

"The result was a set of filters that whilst not vastly visually different, finally became interactive for more of our users as the loaded bundle was reduced to 53KB; a 70% reduction. Once gzipped that reduced further to 13KB."

This post quickly gives a way to measure the “ad weight” rather than “page weight” which is well-known. This is important consideration, given that it represents the bytes attributable to revenue.

"The key takeaway is that today’s ‘standards’ are no longer good enough. We can push the boundaries of web design and development whilst creating a fast, responsive website. We shouldn’t sacrifice performance for creating a beautiful website."

Video streaming is complicated with dozens of potential variables, all of which can affect the quality of the playback to your customers.

"Tinder are still iterating on their Progressive Web App but have already started to see positive results from the fruits of their labor. I’m excited to hear more about their progress in the near future!"

Improving Web Advertising (by changing the Web)

First 5G NR Specs Approved

Le goulot d'étranglement de la performance n'est plus uniquement la bande passante. Le CPU entre aussi en jeu…

The Chrome User Experience Report (CrUX for short) addresses this gap by providing aggregate data from real users across the top sites on the web. With it, you can confidently perform a competitive analysis of sites knowing that the data is backed by real user experiences.

So which method should you use to load your webfonts? Unfortunately the answer is it depends:

• If you’re looking for a quick and simple method you can have working within an hour, use Amazon’s method
• If you want something a bit more thorough and are alright with the limited browser support for now, try using font-display: optional
• And if you really want to make an effort to optimize your webfont loading, take the dive and look into the localStorage technique

"At trivago, we are using Memcached mostly as our caching layer. We have a cache interface that “hides” the logic, so we (the developers) don’t have to think much about its implementation just to know how the interface works."