&gt;  ...I&#x27;m going to evolve my CSS, starting with inline styling, moving out to an inline style node in HEAD, then dynamically loading it from JS as in the Google example, and then finally using a class&#x2F;series of classes.<p>I&#x27;m sure it will load spectacularly fast, but that sounds like a maintenance nightmare.<p>I spent a lot of effort on my &quot;brochure&quot; sites making sure that non-JS users will have a good experience (that includes being able to navigate the site, a privilege an increasingly large number of sites don&#x27;t extend to non-JS users)[1]. Loading even part of my CSS through JS would ruin that experience.<p>1. I do make web <i>apps</i> that require JS, but only for actual applications that work in a similar manner to desktop apps, not for informational sites like blogs.