W3 Total Cache with Amazon S3 and CloudFront

A few days ago Frederick Townes, author of the W3 Total Cache for WordPress has released an update to this wonderful plugin, and yes, it now fully supports Amazon S3 and CloudFront as the Content Delivery Network! This is a major one for me as I manually upload most of the static assets to my CloudFront account which may take quite a lot of time. The W3 Total Cache plugin does that for you in seconds! Post attachments, images, javascript, css.. All those could go to CloudFront in just 4 clicks. Frederick also mentioned that the upcoming update will also be surprising, which keeps me wondering.

I also tried out the other options for page and database caching. A few tests showed up that memcache is faster than APC, so that’s where I stopped at database caching. Page caching was switched to enhanced, which I believe is a new option. The site performance graph at Google Webmaster Tools shows pretty good performance for Novermber and December (very close to 1.5 seconds) although the overall average is still up at 3.5 seconds, which in terms of Google is slower than 59% of sites. This is probably caused by the force majeures in September and October. Page load time peaked at over 7 seconds there.

One more funny fact about Google’s Site performance and Page Speed tools is the “Minimize DNS lookups” section, which most of the time shows up a single entry:

The domains of the following URLs only serve one resource each. If possible, avoid the extra DNS lookups by serving these resources from existing domains: http://www.google-analytics.com/ga.js

Interesting. Perhaps I should copy that javascript file and serve it from my CDN, I wonder if that will work. Oh and then I’ll be missing all the nifty updates to Google Analytics, like the most recent one called Asynchronous Tracking – very neat by the way!

7 thoughts on “W3 Total Cache with Amazon S3 and CloudFront

  1. Tweets that mention W3 Total Cache with Amazon S3 and CloudFront -- Topsy.com

  2. uberVU - social comments

  3. When I have W3 page caching on, Twitter Friendly Links reroutes my link the first time, but if I do it twice, it gives 404 error.

    Any idea how to configure either plugin so that that doesn't happen (please email me direct if you do).

    Kind regards, Steven Smith

  4. Usando Amazon S3 y CloudFront con WordPress, Carrero

  5. Thanks for the update. It's nice to hear that it takes 1, 2, 3, only 4 clicks to make it happen. I'm currently updating an AkronOhioMoms.com blog and this will really help make it fly as my flagship to point clients to.


  6. Quick note on the ga.js issue reported in GWT – this is simply a reporting issue. Google does in fact gzip that file, but not when the user agent is Googlebot (which is used to generate this report). I'm sure they intend to fix this issue as it confuses a lot of people.

Comments are closed.