Paul Buchheit: Make your site faster and cheaper to operate in one easy step

Post by nostrademons » Fri, Apr 17, 2009, 1:23 PM UTC

Confusion wrote: post #6

His speed estimates are wrong, as he should have tested gzipping many small files instead of gzipping one large file. There is a significant difference.

Post by stcredzero » Fri, Apr 17, 2009, 2:28 PM UTC

nostrademons wrote: post #11

Confusion wrote: post #6

His speed estimates are wrong, as he should have tested gzipping many small files instead of gzipping one large file. There is a significant difference.

Why? If you're setting up your website right, you should be serving 1 HTML file + 1 JS file + 1 CSS file + 1 image for each request, and the latter 3 should all be cached indefinitely. (At least for static chrome - if you've got thumbnails, videos, or flash games you can't exactly sprite those.) His test file was 146K, which seems on the high side for HTML only, but I'd imagine serving 1 small file is faster than ser…

Post by ivankirigin » Fri, Apr 17, 2009, 3:17 PM UTC

andr wrote: post #9

That's only one of the needed steps. Adjust your headers so that static items are not reloaded frequently. Use versioned urls (e.g., /scripts/main.js?234) and update the versions only when you change the scripts or CSS. YSlow goes a long way in helping with that kind of stuff. The same applies for S3 uploads. You can pass cache headers in the upload request which will later be used on all downloads.

Post by lucumo » Fri, Apr 17, 2009, 3:33 PM UTC

ulf wrote: post #4

Ardit20 wrote: post #2

Umm I am confused. Is this about compressing the web page itself? I think what takes most of the time to load on my website is the advertisers rather than the content itself. So perhaps this is about large websites like amazon which have large detabases?

I think what he means is just enabling transportation of compressed data from server to client, regardless what you are transporting. The size of your page does not affect the benefits you achieve with this method, which is always less data being transported.

Post by lethain » Fri, Apr 17, 2009, 3:37 PM UTC

ivankirigin wrote: post #15

andr wrote: post #9

That's only one of the needed steps. Adjust your headers so that static items are not reloaded frequently. Use versioned urls (e.g., /scripts/main.js?234) and update the versions only when you change the scripts or CSS. YSlow goes a long way in helping with that kind of stuff. The same applies for S3 uploads. You can pass cache headers in the upload request which will later be used on all downloads.

Do you know something that can modify django templates that contain CSS & JS imports so that the linked version gets updated with each checked in change to the files?