What's your ideal preference vs. practical preference?<p>- Load CSS asynchronously?<p>- Load CSS first and ignore the "Pagespeed Insight" complaint?<p>- It's not a big deal, nobody cares.<p>- Load all styles last.<p>- Load important styles first, unimportant last.<p>- Load CSS in stages and chunk out the visible parts with progressive gzip.<p>- Some other point of view.
I'm a bit confused by the question. On the one hand, it seems like it is targeted at users, since it's about annoying behavior. On the other hand, the options are technical and each of them is great when not leading to the user experience sucking and all of the suck when they lead to the user experience sucking.<p>My preference then is for software that doesn't suck and the way to get there is by testing implementations rather than picking a strategy based on personal bias. CSS should make for a better user experience, and that means that nobody should be aware of it.<p>Good luck.
I'd take a look at the Gaurdian's (Newspaper) web team's presentation on this: Deck: <a href="https://speakerdeck.com/patrickhamann/breaking-news-at-1000ms-front-trends-2014" rel="nofollow">https://speakerdeck.com/patrickhamann/breaking-news-at-1000m...</a><p>Video: <a href="https://vimeo.com/100505617" rel="nofollow">https://vimeo.com/100505617</a>
It's not a big deal, nobody cares.<p>I'd prefer if it is readable without CSS though, as sometimes the CSS won't load from the CDN or whatever. That happens sometimes at home, must be something to do with my ISP.