By default, an <img> takes up zero space until the browser loads enough of the image to know its dimensions.

To workaround this, we can use the width and height attributes, or the aspect-ratio CSS property. Which is best? Depend if the image is content or design!

Pour mettre en forme leurs messages sur les réseaux sociaux, beaucoup de gens utilisent des générateurs de texte en faux gras, faux italique, caractères fantaisistes et abusent des émojis. Cela constitue, la plupart du temps, un détournement d'usage des caractères Unicode. Ce n’est pas sans poser des problèmes d’accessibilité pour les personnes handicapées et, notamment, pour les personnes aveugles utilisant un lecteur d’écran. Le texte ne sera pas lu correctement et sera totalement incompréhensible. Démonstrations et explications.

Instead, hostile poli­ti­cal discus­sions are the result of status-driven indi­vi­duals who are drawn to poli­tics and are equally hostile both online and offline. Finally, we offer initial evidence that online discus­sions feel more hostile, in part, because the beha­vior of such indi­vi­duals is more visible online than offline.

Utiliser un lien HTML classique sera toujours la meilleure des solutions, la plus accessible, la plus utilisable, la plus fiable, la plus robuste, la plus maintenable.

Liste des outils pour sous-titrer vos vidéos et podcasts

Slower connections can result in CLS when lazy loading components that you wouldn’t see on wifi connections.

Either don’t lazy load the component at all or await for the js file to be loaded and mounted.

I want a feature called megablock that blocks a bad tweet, the bad tweet’s author, and every single person who liked the bad tweet, then sounds a brief alarm and makes your phone vibrate

Priority Hints fill the gap of prioritising resources that the browser already knows about against each other.

We are happy to announce that we are open sourcing our first performance quality model that is trained on millions of RUM data samples from around the world free to use for your own website performance optimizations!

[…] the takeaway is pretty simple: text-based LCPs are the fastest, but unlikely to be possible for most. Of the image based LCP types, <img /> and poster are the fastest.

The <div> is the most versatile and used element in HTML. It represents nothing, while allowing developers to manipulate it into almost anything by use...

By using techniques that assess the performance impact of a build in relation to the performance characteristics (magnitude, variance, trend) of adjacent builds, we can more confidently distinguish genuine regressions from metrics that are elevated for other reasons (e.g. inherited code, regressions in previous builds or one-off data spikes due to test irregularities). We also spend less time chasing false negatives and no longer need to manually assign a threshold to each result — the data itself now sets the thresholds dynamically.

We see in the data that the presence of certain errors lead to actions of user frustration that have bottom line implications for the business serving the site. The two most prominent cases of this are reloads and abandonwments (page exits).”
Why? Because this is pretty hard to “understand” that the page exit or the reload in the SR.
Indeed, we just see the error at the very last second and boom, finish (or next replay start in case of reload)

Today in Lyon, France, was the We Love Speed conference. Its focus is on everything related to web performance. Even if the conference talks were only in French, I'll do this recap in English, to let more people learn from it.

In the new responsiveness metrics, we measure the latency of user interactions, how your customers navigate and act on your website, rather than individual events. A user interaction, such as tap (click), drag, and keyboard interaction, usually triggers multiple events.

I’ve learned that one reason there isn’t a good reference for the role of the CTO is that the size of the company and the expectations of the CEO define the job.

In summary, it claims that Google falsely told publishers that adopting AMP would enhance load times, even though the company’s employees knew that it only improved the “median of performance” and actually loaded slower than some speed optimization techniques publishers had been using.

It’s easy to get excited about new techniques for measuring and improving site speed but this focus on the technical side of performance can lead us to think of speed as a technical issue, rather than a business issue with technical roots.

Almost half of all pages that scored 100 on Lighthouse didn’t meet the recommended Core Web Vitals thresholds.
[…]

1. If you're going to talk about the performance of a production site, use real-user data.
2. If you're going to use a single number to cite a performance result, specify where that number falls in the distribution.
3. When talking about real-user performance, be specific about the time period.
4. If you do want to brag about your Lighthouse score or other lab results, do so in the context of the larger performance story.

Core Web Vitals is a measurable SEO ranking factor. This data study shows changes seen during the Page Experience Update July-Aug 2021