In short, we wanted our list of top web performance recommendations to focus on:

• Recommendations we believe will have the largest real-world impact
• Recommendations that are relevant and applicable to most sites
• Recommendations that are realistic for most developers to implement

Since there is only one Main Thread responsible for all these Tasks, any Task that takes a particularly long time to execute will clog up the thread and degrade user experience.

There’s a huge focus recently on JavaScript bundle size: how big are your dependencies? Could you use a smaller one? Could you lazy-load it? But I believe we focus on bundle size first and foremost because it’s easy to measure.

[…] you could imagine some basic stats around initial CPU execution time, memory usage, and disk usage that wouldn’t be impossible to measure in an automated way.

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