- Load CSS asynchronously?
- Load CSS first and ignore the "Pagespeed Insight" complaint?
- It's not a big deal, nobody cares.
- Load all styles last.
- Load important styles first, unimportant last.
- Load CSS in stages and chunk out the visible parts with progressive gzip.
- Some other point of view.
I have CSS disabled and if your site isn't easily navigable without CSS, I leave.
E:
If your page doesn't make sense without CSS enabled, your content is a mess and no amount of design is going to make it better.
Inline styles are rare enough and usually sensible enough that I don't mind them when they appear. I have a bookmarklet to remove them on a per-page basis if needed.
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.
Good luck.
Video: https://vimeo.com/100505617
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.