Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How We Achieved a .50s Page Load

blog.netdna.com

Post reply on HN
Print view View original

21–25 of 25 posts

Re: How We Achieved a .50s Page Load

#21

Post by DrJ »

I think there are 3 things that should be applied to anyone serving images.

1. Expires Header (for static) 2. Cache-Control Headers (for less static) 3. KeepAliveTimeout (might be a double edged sword)

and you can set the first 2 on Amazon S3

Re: How We Achieved a .50s Page Load

#22

Post by nycacorp »

DrJ wrote: post #21

I think there are 3 things that should be applied to anyone serving images. 1. Expires Header (for static) 2. Cache-Control Headers (for less static) 3. KeepAliveTimeout (might be a double edged sword) and you can set the first 2 on Amazon S3

true you can also set these on the NetDNA CDN Platform through their vhost modification service. also any origin server should be able to set these as well and any CDN honor those settings

Re: How We Achieved a .50s Page Load

#25

Post by kerno »

tjasko wrote: post #6
kerno wrote: post #4

Wow, that is really fast. This article is really detailed and has given me lots of things to look at tonight. I'm assuming based on the WPMinify mention that this is a WP site - would be curious to know if the speed improvements were all in html/css/js and caching, or if there was anything done to WP as well.

Thanks! We use WP Engine to host the site, which they have a pretty nice system set in place to host WordPress. They have a page on their system architecture here: http://wpengine.com/our-infrastructure/ Basically, it just comes down to caching in a brilliant way. But other than that, we did not do anything special to WordPress itself.

Hi tjasko - that's for the follow-up info. We're on WPEngine as well and now I'm excited to see how much of an improvement we can make using the techniques you covered. Thankyou
Post reply on HN