title: Does inlining Critical CSS worth?
body: <p>Google Pagespeed complains when you have blocking CSS in an external file. In HTTP/1 this probably makes sense, but what about now with HTTP/2 ?</p>
  
  <p>If you inline critical CSS (above the fold), that bytes still need to download, parse and everything else, all before the document renders.</p>
  
  <p>With HTTP/2, there is no need to make another connection since the same can be reused, so that is not an overhead. Plus, with server push you can even push the CSS file before it's being requested.</p>
  
  <p>So... is inlining critical CSS still a recommended thing?</p>
  
  <hr>
  
  <p>I agree that in heavy sites, you probably don't want to download all CSS. For example if you are visiting the gallery, you would only need gallery.css, not profile.css, not forum.css, etc. But that is manageable with chunks and other techniques (and still using external css files, no need to inline them)</p>
  
  <p>Inlining also makes CSS not cacheable.</p>
  
  <p>I am missing something?</p>
  
  <hr>
  
  <p><em>This has nothing to do with the possible duplicate question. Whoever marked this as duplicated has no idea about what critical CSS is or probably didn't even have read this question.</em></p>