"With the DNS prefetching flag in Google Chrome on Android enabled, Chrome scans the page for clickable links and resolves the URLs to IP addresses. By the time you head to any of the pages, their addresses will have been returned to your device, mitigating any DNS speed issues — the only bottleneck will be your own connection. (Optionally, it will use your device’s own DNS servers and won’t touch Google’s unless you want it to.)"

"Some of these technical aspects are often overlooked. Also, don’t be afraid to change things around and set yourself up to test several variants of code on your website."

Just because your site isn't for emerging markets, doesn't excuse you from web performance optimisation

Hell is other people’s JavaScript.

TL;DR : Reduce the weight of your files by using optimization strategies that depend on the content and purpose of your videos ; Optimize streaming by encoding your videos to serve metadata as soon as possible ; Propose alternatives to MP4, such as WebM.Be careful with autoplay, consider dedicated solutions for Full HD and don’t hesitate to hide videos when needed.

"webpack is a fantastic, versatile, tool that does not need to cost the earth. These techniques have helped us reduce our median build time from 170 to 17 seconds and, while they have done much to improve the deployment experience for our engineers, they are by no means a complete work."

JavaScript a un coût (The Cost Of JavaScript). Je continue de préférer, tel un vieux développeur que je suis, à construire des coquilles. Je ne dénigre pas le JavaScript ou les applications, mais quand on code un site qui va être chargé par tous types d’utilisateurs, il est important de prendre en compte les cas de faibles connexions.

Using page speed in mobile search ranking

"Third-party scripts are probably the #1 cause of poor performance and bad UX on the web. It's no wonder things like AMP exist. The fact that it disallows third-party scripts is probably the largest contributor to it making sites fast. Controversial as hell, though, in its other choices."

"Instead of search results being generated favoring the desktop version of a site, Google will begin to favor mobile versions. If you have a half-hearted mobile site and a full-fledged desktop site, you better be careful once Google starts favoring the mobile site."

"In Drupal 8, there are specific tools and modules to optimize the site performance."

"Publishers should not be compelled by Google’s search dominance to put their content under a Google umbrella. The Web is not Google, and should not be just Google."

"Once web teams have policies like that in place for popular searches that bog down web performance during beyond-peak, it’s easy enough to set up a dashboard with toggles for web teams to switch between rich and powerful searches and redirects when needed."

"The HTTP Archive is open source and the raw data is available to download. If you want, you can download all of the data, process it locally and query it as much as you want. However, that would require a lot of effort to set up. Google BigQuery makes this much easier, since the data is already loaded and can be easily queried. And because of the processing power behind BigQuery, even some of the most complex queries you write will run extremely fast."

"In a year since Facebook’s blog about Cache-Control Immutable, we can see that it’s usage has spread beyond Facebook and is being used by a handful of large 3rd parties and ~4150 additional domains. Across all of the pages in the HTTP Archive, 2% of requests and 30% of sites appear to include at least 1 immutable response. Additionally, most of the sites that are using it have the directive set on assets that have a long freshness lifetime."