Un essai jouable sur la forme que prend une société

What these metrics do give you is a baseline to look at to make an informed decision if the feature you are shipping is worth the overhead. That's something between the site and it's users to decide in many ways, but Web Vitals gives some the tools to help quantify that.

Le problème n’est pas de se signaler « mais moi je n’ai jamais tué personne » comme ils disent « mais moi je ne suis pas un violeur ». Car le privilège, c’est avoir le choix d’y penser, ou pas. Je ne peux pas oublier que je suis une femme. Mais je peux oublier que je suis blanche. Ça, c’est être blanche. Y penser, ou ne pas y penser, selon l’humeur. En France, nous ne sommes pas racistes mais je ne connais pas une seule personne noire ou arabe qui ait ce choix.

• Get a DevTools performance trace for a page load
• Get a DevTools trace with screenshots
• Get a DevTools trace and extract filmstrip screenshots
• Get a DevTools trace for a user interaction
• Get Runtime performance metrics
• Generate a Lighthouse report
• Extract Lighthouse performance metrics
• Emulate a slow network
• Emulate a slow network and CPU
• Test your site renders with JavaScript disabled
• Get Navigation Timing API metrics
• Measure First Paint and First Contentful Paint
• Measure Largest Contentful Paint w/PerformanceObserver
• Measure Cumulative Layout Shift w/PerformanceObserver
• Measure SPA metrics with Next.js
• Get DevTools-specific metrics: Frames Per Second
• Measure memory leaks
• Override requests with Request Interception
• Block third-party domains
• Code Coverage for JavaScript and CSS

We have seen that there can be many reasons for users to opt-in to save-data, and that the performance delivered to devices doesn’t (yet) vary much based on the hint. A lack of awareness from both developers and web users mean that a potentially valuable web platform feature is under utilized.

[…] est le premier moteur de recherche de livres en France. Il fédère 16 portails de libraires indépendants, nationaux, régionaux ou spécialisés, soit plus de 1000 librairies implantées sur l'ensemble du territoire.

Un générateur de Lorem Ipsum sert à générer du faux texte en latin pour remplir des maquettes.
Un générateur de Lorraine Hipseaume sert à générer de faux prénoms et noms français pour remplir des maquettes.

So you have to be really careful when using this metric, the LCP is not always tracking the element you think

So it looks as if a white academic male in hyper-individualist America thought that everyone in the world is like him. What a surprise.

And for what? Again - there is a swath of use cases which would be hard without React and which aren’t complicated enough to push beyond React’s limits. But there are also a lot of problems for which I can’t see any concrete benefit to using React. Those are things like blogs, shopping-cart-websites, mostly-CRUD-and-forms-websites. For these things, all of the fancy optimizations are optimizations to get you closer to the performance you would’ve gotten if you just hadn’t used so much technology.

The issue with most slow JAMstack sites is that they load a loooot of JavaScript. Remember that any added JavaScript has to be sent to the browser, which will also need more computation for it. It quickly impacts performance.

Web Performance and Web Performance Optimization are still valid and descriptive terms for our industry, but we might benefit from a change to our language when working with others. The language we use could be critical to the success of making the web a faster and more accessible place.

It would seem that, realistically, the benefits of Brotli over Gzip are slight.
[…]
if you’re faced with the prospect of weeks of engineering, test, and deployment efforts to get Brotli live, don’t panic too much—just make sure you have Gzip on everything that you can compress (that includes your .ico and .ttf files, if you have any).

Sadly, I think the current state of “modern” web development reverses that principle. Developer efficiency is prized above all else. Like I said, that would be absolutely fine if we’re talking about technologies that only developers are exposed to, but as soon as we’re talking about shipping those technologies over the network to end users, it’s negligent to continue to prioritise the developer experience.

Cette formation à l’accessibilité numérique apporte les outils et ressources indispensables pour concevoir et développer des pages web conformément au RGAA. Elle peut s’accompagner d’une certification.

The bottom line is this: we don’t have control over how content is consumed. Users have personal browser settings, the ability to zoom in and out, and various other ways to customize their reading experience. But we do have best CSS best practices we can use to maintain a good user experience alongside those preferences

J’essaye de travailler à rendre le web meilleur et notamment accessible aux personnes handicapées. C’est possible avec mon métier mais on est bien peu de chose face à l’immensité du web.

@media (prefers-color-scheme: dark) {
   filter: invert(90%) hue-rotate(25deg);
   img, video, iframe {
       filter: invert(100%) hue-rotate(-25deg);
   }
}

You know, faster websites mean happier users. It’s absolutely in no doubt. And I just don’t get it, to be honest. I don’t get how people can be working on the web claiming to be doing user centered design and yet, at the same time, ignoring this huge factor.