With revived interest in using my Amazon AWS account again, I’ve started to setup this WordPress blog for using Amazon AWS Cloudfront CDN for serving static files for better pages speed for all geographic visitor locations. The Amazon Cloudfront CDN is using a custom subdomain, wp7cdn.centminmod.com setup using a hosted zone subdomain only on Amazon Route53 DNS services. The subdomain hosted zone is configured as an A record domain alias target to the actual Cloudfront distribution I created.
Using WordPress CDN hosting to improve your page speed, latency and TTFB (Time To First Byte) are a common web site optimization technique to bring your static file content closer to your visitor’s geographical location. If you haven’t already tried using CDN hosting, I suggest you give it a go 🙂
Currently, I have Amazon Cloudfront configured to serve WordPress CSS, JS and to serve WordPress uploaded attachment and images. This is done via two WordPress plugins which have CDN support, Autoptimize and WordPress Super Cache.
You can check the Amazon Cloudfront custom subdomain’s headers to see whether there’s a Miss or Hit from cloudfront when loading Amazon Cloudfront served static files.
curl -I http://wp7cdn.centminmod.com/favicon.ico HTTP/1.1 200 OK Content-Type: image/x-icon Content-Length: 603 Connection: keep-alive Server: nginx centminmod Date: Mon, 17 Nov 2014 13:04:07 GMT Last-Modified: Wed, 20 Feb 2013 06:51:22 GMT ETag: "5124726a-25b" Expires: Wed, 17 Dec 2014 13:04:07 GMT Cache-Control: max-age=2592000 Accept-Ranges: bytes Age: 1047 X-Cache: Hit from cloudfront Via: 1.1 b23c103157f513f91600fd15baee29c1.cloudfront.net (CloudFront) X-Amz-Cf-Id: aSNGeADwogEk1t0fx9iTdEFsojOz0QiTC7exSLYSO3jOl7j3qcaOaw==