"...I determined that unless you’re a very frequent visitor to one of our sites, you’re visiting us with a cache that is effectively empty downloading many or all of the objects on our homepage. Why? Because we update our pages multiple times per day."
Totally wrong. His front page is 11.7K html and 278K all other things (css, js, img etc, based on YSlow data). His site's burden to a visitor with a primed cache is 22K. Even if he updates all the content in a single day, his non-primed data will be 22K and that's all.
His site does not employ far-future expiration day strategy. Steve Souders explains them all, every web hacker should read his books.
First, thank you for taking the time to investigate one of our sites and do some research. Which site did you look at?
Beyond that, I'm not sure I follow your math...how did you calculate that "Even if [I] updates all the content in a single day, his non-primed data will be 22K"?
7 comments
[ 2.1 ms ] story [ 37.3 ms ] thread"...I determined that unless you’re a very frequent visitor to one of our sites, you’re visiting us with a cache that is effectively empty downloading many or all of the objects on our homepage. Why? Because we update our pages multiple times per day."
Totally wrong. His front page is 11.7K html and 278K all other things (css, js, img etc, based on YSlow data). His site's burden to a visitor with a primed cache is 22K. Even if he updates all the content in a single day, his non-primed data will be 22K and that's all.
His site does not employ far-future expiration day strategy. Steve Souders explains them all, every web hacker should read his books.
Plus, not sure why you think the user wouldn't need to redownload the assets that change each day.
First, thank you for taking the time to investigate one of our sites and do some research. Which site did you look at?
Beyond that, I'm not sure I follow your math...how did you calculate that "Even if [I] updates all the content in a single day, his non-primed data will be 22K"?