Google Pagespeed complains when you block CSS in an external file. In HTTP / 1, this probably makes sense, but what about HTTP / 2?
If you embed critical CSS (above the crease), then these bytes still need to be loaded, parsed, and everything else, all before the document is rendered.
With HTTP / 2, there is no need to create another connection, as it can be reused, so this is not an overhead. In addition, when you click on the server, you can even click on the CSS file before it is requested.
So ... in short is critical CSS still recommended?
I agree that on heavy sites you probably don't want to load all the CSS. For example, if you visit a gallery, you only need gallery.css, not profile.css, not forum.css, etc. But this is manageable with chunks and other methods (and still using external css files, there is no need to embed them)
Nesting also makes CSS non-cacheable.
Am I missing something?
This has nothing to do with a possible duplicate question. Anyone who has flagged this as duplicate does not know what critical CSS is or may not even have read this question.
source
share