With HTTP/2 asset pipelining, adding stylesheets directly above the html they affect gives you the quickest display of content from first byte.
It’s common to bundle all of a site’s CSS into one or two resources, meaning the user downloads a large number of rules that don’t apply to the current page. This is because sites can contain many types of pages with a variety of “components”, and delivering CSS at a component level hurts performance in HTTP/1.
This isn’t the case with SPDY and HTTP/2, where many smaller resources can be delivered with little overhead, and independently cached.
Read more from the source: jakearchibald.com
HTTP2 will change the development workflow: here’s a primer on how it is faster than HTTP1
From Reversim Summit 2015 http://summit2015.reversim.com/
Watch the 5-minute video on YouTube
HTTP2 is based on Google’s SPDY and will change the way you minify and bundle assets
HTTP2 will mean a change in how we should build websites. The best practices of HTTP1 are harmful in a HTTP2 world.
Remember the (hacky) practices below? Well with HTTP2 they are obsolete and even detrimental to performance.
– Image sprites
– Concatenating JS and CSS
– Serving assets from a cookie-less domain.
– Creating different domains or sub-domains to host assets like images.
Read more from the source: mattwilcox.net