This is not a React hit piece, but rather a plea for consideration of how we do our work. Some of these performance pitfalls can be avoided if we take care to evaluate what tools make sense for the job, even for apps with a great deal of complex interactivity.
[…] if you use React or any VDOM library, you should spend some time investigating its impact on an array of devices. Get a cheap Android device and see how your app feels to use. Contrast that experience with your high-end devices.

The implementations of Back/Forward caches in popular browsers are helping to improve this experience even further - which has the benefit of significantly speeding up the web for up to 20% of navigations!

Now that you know these metrics, we can use them to understand what’s happening on our sites and to ask better questions.

Fortunes are made and lost based on how brands thread the needle between site speed and functionality. Despite this, the Retail Systems Research (RSR)’s survey reveals the average retailer’s website is still too slow, and their mobile sites are even slower.

Even worse, many have no idea how they stack up.

Leur donner un nom c’est donner une importance à ce qui ne l’est pas. Le nom n’est pas important. Ce que l’on en fait l’est.

[A-zÀ-ú] // accepts lowercase and uppercase characters
[A-zÀ-ÿ] // as above but including letters with an umlaut (includes [ ] ^ \ × ÷)
[A-Za-zÀ-ÿ] // as above but not including [ ] ^ \
[A-Za-zÀ-ÖØ-öø-ÿ] // as above but not including [ ] ^ \ × ÷

… ~50% savings compared to JPEG, and ~20% savings compared to WebP.
… can be lossy or lossless, has the ability to use an alpha channel (transparency for UI and design elements), and even has the ability to store a series of animated frames (think lightweight high-quality animated GIFs).
… one of the first image formats to support HDR color support; offering higher brightness, color bit depth, and color gamuts.

Results show that enabling TLS 1.3 is a good idea. It offers more security and better performance for your users. It’s also worth noting that TLS 1.3 will be a requirement to use the QUIC transport layer network protocol in the future. This will pave the way to HTTP/3. And once 0-RTT becomes more prevalent, for repeat website visits the purple on the graphs displayed above will disappear completely. Even faster connections for all (at least for those that use a browser that supports it anyway).

Un précis de vocabulaire pour se rappeler des termes CSS.

Complémentaire à votre outil de préparation à la certification et adapté au travail en équipe, ce "tableau vivant" vous permettra de visualiser votre avancement, pour la préparation à la formation comme pour la mise en oeuvre (audit)...
Comme c'est un modèle, vous pourrez partager vos commentaires, vos exemples, captures d'écrans, etc. en équipe restreinte.

Par son côté visuel, un emoji choisi de manière pertinente peut apporter de l’impact à un message, pour peu qu’on respecte quelques bonnes pratiques.

A wonderful pen by Vincent Valentin

Une explication très complète et didactique sur les privilèges, le racisme, le racisme ordinaire, la fragilité blanche…

We must start by trying to use the option that damages the environment least, and that is text. Don’t assume that images are automatically more powerful than text. Sometimes, text does the job better.

[…] there is one less round trip until Application Data can be sent in TLS 1.3 as compared to TLS 1.2. This significantly improves performance especially on high latency networks.

However, I noticed that our max TLS version was 1.2 rather than the newer and faster 1.3, as 1.3 removes an extra RTT for a faster handshake. Turns out the version of nginx-ingress we were using was still using 1.2 only as default. A quick ConfigMap change later, and we were on 1.3.

track and measure the performance of sites that use popular JavaScript frameworks and libraries.

Automates ImageOptim, ImageAlpha, and JPEGmini for Mac to make batch optimisation of images part of your automated build process.

It would be useful to have insight into the moment when assistive technology is able to interact with and communicate page content, so that we can know when a page is “ready” for all users, and not just some.
[…] It’d be interesting to know which existing metrics are irrelevant to assistive tech
[…] it might be interesting to measure “jank” and stability in the process of arriving at a usable accessibility tree.
[…] how are metrics like First Input Delay translating to the interaction time that someone experiences when using assistive technology?

Nous pourrions par exemple proposer pour les personnes concernées par le sexisme, donc par la domination des hommes cis hétéro, d’employer le terme de : personnes sexisé.e.s.

La discrimination ne nait pas de qui vous êtes mais du regard discriminatoire.