tl;dr: Google wants you to build PWAs, reduce JavaScript file size, use Web Components, and configure autofill. They announced only a handful of features around payments, authentication, Android Trusted Web Activities, Chrome Dev Tools, and the Chrome User Experience Report.

"Google has all the ability in the world to reward and punish sites based on their performance without fracturing the web in the process."

"After creating it I used it to learn some more about Webpack and Web performance in general. In this article I’ll show you everything I did to make the app load from 2690ms down to 170ms."

"Performance matters. Next year, we’re thrilled to venture to London for our brand new conference fully dedicated to everything front-end performance. Dealing with ads, third-party scripts, A/B testing, HTTP/2, debugging, JAM stack, PWA, web fonts loading, memory/CPU perf, service workers. Plus lightning community talks."

"Netflix uses React on the client and server, but they identified that the client-side portion wasn't needed for the first interaction, so they leaned on what the browser can already do, and deferred client-side React. The story isn't that they're abandoning React, it's that they're able to defer it on the client until it's was needed. React folks should be championing this as a feature."

"HTTPS is easier and cheaper than ever before, and it enables both the best performance the web offers and powerful new features that are too sensitive for HTTP. There’s never been a better time to migrate! Developers, check out our set-up guides to get started."

"That’s a particularly low blow, because it’s such a bait’n’switch. One of the reasons why AMP first appeared to be different to Facebook Instant Articles or Apple News was the promise that you could host your AMP pages yourself. That’s the very reason I first got interested in AMP. But if you actually want the benefits of AMP—appearing in the not-search-results carousel, pre-rendered performance, etc.—then your pages must be hosted by Google."

"When we’re evaluating technology, or discussing a particular strategy, we can’t give a project a pass because anyone can open a pull request. Instead, it’s worth asking ourselves Franklin’s questions: when a site adopts AMP, who benefits? And who, or what, assumes the risks in using AMP?"

Let’s Encrypt (SSL)
HTTP/2
Brotli compression
WebP images
Content delivery network

"It is unclear how many sites have already switched over to the mobile-first indexing process, but, when I asked Illyes to clarify what he meant by “a few sites,” he said a few relative to the Google index. So that could be quite a large number of websites."

"You have optimized every line of code of your site / mobile application, used all the techniques at your disposal to have the fastest loading time possible. Yet, users still complain about the slowness. Let’s learn to use different design techniques and UX to work performance also at the level of user perception."

"C’est Amazon qui mène assez nettement les débats en étant la seule enseigne du panel à obtenir un Speed Index inférieur à 2 secondes (1895ms), suivi par Cdiscount (2375ms) et Booking.com (2599ms). À l’autre bout du classement, les 5 dernières enseignes (Castorama, Airbnb, Voyages-sncf, Carrefour et E.Leclerc) dépassent quant à elles les 6 secondes et E.Leclerc ferme la marche au-delà des 11 secondes… Soit une page plus de cinq fois plus lente à l’affichage qu’Amazon."

"The report is a public dataset of key user experience metrics for top origins on the web. All performance data included in the report is from real-world conditions, aggregated from Chrome users who have opted-in to syncing their browsing history and have usage statistic reporting enabled."

Lightweight JavaScript library for accurate web loading progress.