> The problem with inlining all CSS is serving all the global styles all over again with every page load. > You're gaining a great first impression at the cost

> The problem with inlining all CSS is serving all the global styles all over again with every page load. > You're gaining a great first impression at the cost of a poorer experience for every subsequent page load. Yep, it's unfortunate we still have to make tradeoffs like this. At least in this case, it's less than 8KB added per page vs something more complicated that might break. HTTP push was getting closer to offering some alternative like what you're suggesting (the server pushes the CSS file to the client in parallel to the initial HTML page, and the client can say if it already has the CSS file) but it's being deprecated now.