Performance

• Hot from the oven: AMP project!
  The web today is many things: an application platform, an e-commerce platform, a content platform, a gaming platform, and so much more. The AMP project decided to focus entirely on static content as it lends itself to more radical optimization approaches that are easier to apply across the board.
  It’s all on Github so join the party. Btw, you can see the WordPress moving into producing AMP pages.
  
• Tools like ‘srcset’ allow developers to serve an optimized image variant in a responsive way, but it can be cumbersome and inefficient to use in practice. Developers can now negotiate with the server (resource selection with client hints) to download the best image variant for a device using straightforward HTTP request headers. These headers communicate DPR, Viewport-Width, and the intended display width of the resource being fetched to the server.
  
  
• Sites can specify origins that Chrome should preconnect to in order to improve performance.

Service Worker

• Cache.addAll() is now supported, removing the need for polyfills enabling bulk interactions with the cache.
• The Fetch API now supports Request.redirect, allowing more control over redirects.
• Resource Timing extensions to the Performance interface are now available without prefixes.
• As part of our continuing policy to remove powerful APIs on insecure origins, the Cache API is now restricted to HTTPS.

CSS

• Developers can now use CSS.escape(), eliminating the need for complicated string escape code while handling user-generated identifiers.
• The CSS intrinsic sizing values, which allow boxes to fit their contents, are no longer prefixed.
• Animating objects along author specified paths – Developers can now animate any graphical object along an arbitrary path declaratively as a CSS property, allowing simpler code that doesn’t block rendering or input.

Other Stuff

• Mobile Improvements: Sites launched from the home screen can now modify the default color of Chrome’s UI by specifying a theme color in their web manifest instead of a meta tag.
• WebRTC – Timer-based polling is no longer necessary to use WebRTC DataChannels, making them more efficient and convenient.
• DevTools – It has a better tool tips and custom network profiles.
• ES2015 specification – Chrome now supports the spread operator and new.target.
• Developers can now disable Chrome’s default scroll restoration behavior on history navigation when it interferes with the app’s user experience.
• Sites that have been added to the home screen can now set a background color to show while resources load.
  See below a good example of this cool feature. Btw, this web app is a good one…

Want to watch instead of reading?