Hi everyone!

I am planning on implementing HTTP Compression in my site, I have been reading and I see big advantages by "gzipping" content from server so that bandwidth could be reduced when reached to client-side.

From what I read, I could add the following pro's:
- Content is compressed when sent from server to client, leveraging bandwidth traffic, reaching in a "faster" way to the user.

And the con's I understand:
- Compression algorithm requires CPU loads
- Compression takes place with text content, not images, etc

Am I missing any other important thing to consider?

Hi

I have turned this on, and the difference is huge if you have a slow internet connection. The CPU usage on the web server increases, but not very much. So unless the CPU on the server is very slow, there will not be a problem. You save a lot of bandwidth, and also, since the server spends less time on each client, I think the difference on server load is not much different.

If you use Apache2, it's very easy to set up:

sudo a2enmod deflate

But if your webserver has lots of PHP scripts, it will not make a difference. To get PHP scripts compressing, you need to edit your php.ini:

zlib.output_compression = On

Thanks a lot!! That was exactly what I was looking for , I'll implement it right now to see the improvements