I do not deny that CDN'ing the CSS assets can increase the HTTP pipeline. The point is that sometimes that additional DNS lookup can be hazardous. If it's not just outright slow, like I showed in 2009: http://www.peterbe.com/plog/slow-dns it could be yet another thing to go wrong like I showed above where rackcdn.com and contextly.com were both down rendering the site useless.
Comment
Hrm, it's well known that JavaScript blocks the DOM from downloading anything else:
https://developers.google.com/speed/articles/include-scripts-properly
Not CDN'ing the JS might be a fair call. But for CSS assets it increases the HTTP pipeline.
Replies
I do not deny that CDN'ing the CSS assets can increase the HTTP pipeline. The point is that sometimes that additional DNS lookup can be hazardous.
If it's not just outright slow, like I showed in 2009: http://www.peterbe.com/plog/slow-dns it could be yet another thing to go wrong like I showed above where rackcdn.com and contextly.com were both down rendering the site useless.