Nouvelle proposition dans le monde du RUM, rejoint SpeedCurve dans la cour des Dashboard de Perf Web. Ici, focus sur le monde de la Presse.
Neuroscience de la performance Web Desktop et Mobile.
Ajout de contenu dynamique en JS, sans gêner l'accessibilité.
"JS Manners is a tool to score scripts that 3rd parties (people or companies outside your dev team) provide for you to put on your page."
"PhantomJS-based web performance metrics collector and monitoring tool"
"Charles is an HTTP proxy / HTTP monitor / Reverse Proxy that enables a developer to view all of the HTTP and SSL / HTTPS traffic between their machine and the Internet. This includes requests, responses and the HTTP headers (which contain the cookies and caching information)."
"Sitespeed.io is an open source tool that helps you analyze your website speed and performance based on performance best practices and metrics. It collects data from multiple pages on your website, analyze the pages using the rules and output the result as HTML or JUnit XML."
List of various Web Performance Tools
Excellente Cheatsheet Git, qui a le mérite de souligner les interactions entre les différentes zones du dépôt.
"The abandonment rate for mobile shopping carts is 97%, compared to 70-75% for desktop carts. We also know that performance is a significant abandonment factor. Slow pages are the number one user complaint around mobile sites, ranking even higher than site crashes. And when faced with a bad mobile shopping experience, 43% will go to a competitor’s site next."
"One good practice in web performance optimization is to “put script at bottom”.
The reason is that while scripts are loading, most browsers block others components from loading.
When you put your scripts at the bottom of the HTML document, all components can be loaded without delay, and, in the end, scripts can be loaded.
However, doing this way has some drawbacks :
One is that the loading of externals scripts is delayed after all other components. Then, browsers have to execute it and the onload event of the page can also be delayed due to this late loading.
Another major drawback is the presence of inline <script> in the <body>.
Of course, as externals scripts are loaded at the end of the page, any inline script that needs to use it has also to be pushed at the end of the page. This can be quite easy when the HTML page is hand-made.
But in most cases, HTML document scripts are added by several modules provided by a CMS or jQuery plugins. And these modules often have inline javascript in order to initialize behaviors related to the functionality they provide, when the document is ready.
Especially when working with jQuery, if you load it at the bottom, all preceding jQuery('document').ready() calls will fail.
I’ve been wondering for a long time if it would be possible to get rid of these drawbacks while reaching the following goals:
early external jQuery loading
non blocking jQuery loading that allow other components on the same page to be loaded in parallel, including jQuery plugins
non blocking inline script in the HTML document, that could call jQuery('document').ready(), even when jQuery and its plugins havent’ been loaded yet.
jQl is my solution."
Les données viennent de l'ancien tableur créé par Eric Daspet qui est depuis tombé en désuétude.
Plugin Grunt permettant d'exécuter Google Pagespeed Insights en ligne de commande.