Reply to thread

Sorry for posting to an old thread, but I would like to second the request with more arguments for having CSS served from a separate URL.

 

We want to serve all static content from CDN. Even though CSS is "generated dynamically", it's still static. It very rarely changes.

 

Our CDN fetches content from our servers using origin pull, and would hence be able to cache the css.php without a problem.


There are two key arguments for serving from a separate CDN domain:

  1. serving from a CDN moves the content closer to the client - this can have a huge impact for some users
  2. using a cookieless domain makes the request header smaller and hence the request faster

Even though the content is cached on both the server side and client side (Expires: Wed, 01 Jan 2020 00:00:00 GMT), the "empty cache" experience for a first time visitor is presumably faster if majority of the content (i.e. CSS, JS and images) are served from a quick server close to the client.


Back
Top Bottom