Not necessarily. We visit tons of sites and a small blog has slim chances of getting its assets into the cache in the first place (if browsers put every asset we browse in the cache it could even reach 1GB per day or so eaten by the cache...).

And most blog visitors are traffic by some random success post linked from some popular site or one-off search traffic.

So, they won't stick around for cache to matter anyway -- better give them a nicer first experience in the off chance that they do stick because of that.

Fast then fast is better than slow then fast.

Once zipped the css is tiny anyways.

HTTP2/SPDY makes inlining css irrelevant