>> CSS files can be marked "to be cached forever" (which can be done if
>> they have content-based filenames).
>>
->> In terms of time, [[!wp HTTP_pipelining desc="according to Wikipedia"]]
+>> In terms of time, [[!wikipedia HTTP_pipelining desc="according to Wikipedia"]]
>> browsers don't generally pipeline requests, so the page won't finish
>> loading until one round-trip time per uncached CSS file has elapsed.
>>
>> think that's the case (apart from possibly local.css, which is why
>> I'm not sure whether to include it in this).
>> --smcv
+
+>>> I must admit that I am not aware of how those several CSS inclusion lines
+>>> tend to make browsing less smooth. Please withdraw my comment.
+>>>
+>>> As you pointed out, CSS inclusion is more painful than it should be, and
+>>> your proposal seems to answer that. Go ahead! --[[Louis|spalax]]