It slows things down especially because the browser will likely have to layout/re-render the page everytime a new chunk of CSS arrives. Generally avoid splitti

It slows things down especially because the browser will likely have to layout/re-render the page everytime a new chunk of CSS arrives. Generally avoid splitting CSS. Even if you don't use all your CSS on every page, a cached 100kb CSS file will outperform a bunch of unique-per-page 25kb CSS files everytime (especially since it's 0 requests for the second page). Except for dial-up probably. It may be beneficial to split CSS files somewhere above the 300kb mark, but I wouldn't know. My one-page-app is only about 500kb over the wire, including CSS, JS, Fonts and HTML. ~30KB of that is CSS. I've been optimizing that for years though.