I've been doing a lot of reading about compressing your servers output stream.

Before gzip compression, the bink.nu homepage was about 321k! This means that it would take about 89 seconds for a normal 56k user to download the page.

After gzip compression, the page is 79k! Now it takes the same 56k user 22 seconds to download the page.

If your server can support a little extra load (to compress the output stream), then I highly reccomend using a output stream compression engine!

Here is a list of .NET/ISAPI (for IIS) modules that I'm aware of:

.NET Modules
ASPAccelerator.NET
http://www.intesoft.net/aspaccelerator/
Blowery HttpCompression Module
http://www.blowery.org/code/HttpCompressionModule.html

ISAPI Filters
XCompress
http://www.xcompress.com/
IIS Accelerator
http://www.iisaccelerator.com/
SqueezePlay
http://www.innermedia.com/
jetNEXUS for IIS
http://www.preactholdings.com/perfor...xus/jet-nexus/
PipeBoost
http://www.pipeboost.com/
TurboIIS Pro
http://www.objectsfarm.com/turboiis/

Maybe someone can post some good ones for Apache..

For Apache, in httpd.conf, look for this line:

AddEncoding x-gzip gz tgz

It's usually on by default, but if it isn't, you can add/uncomment it within <IfModule mod_mime.c> so it reads like this:

<IfModule mod_mime.c>

AddEncoding x-compress Z
AddEncoding x-gzip gz tgz

If you don't have that module loaded (mod_mime.c) then it won't do you any good, so check the Modules section to ensire it's being loaded.

I think a web page that you download to your system shouldnt' be more then 64k max.
It is kind of unspoken rule between web developers. And I agree.

100+ is maybe because its a big article.
250+ is maybe because it has a big image file
but
300+ is just too big.

gzipped pages should load instantly, for they wont result in more then 12k per page.