Webmastersite.net
Register Log In

gzip web page compression

Comments on gzip web page compression

Daniel
Member

Usergroup: Member
Joined: Jul 08, 2009

Total Topics: 17
Total Comments: 31
Daniel
Posted Aug 25, 2010 - 1:53 PM:

You can make your page more then 2x fast if you only write a single line of code.

I didn`t believe my eyes as I first saw the effect.
It`s look like magic but it isn`t.
All you have to do is to write the following in your .htaccess :


php_value output_handler ob_gzhandler


Thanks to Paul and his powerfull WSN Links script there is an easy way to do this.
Just write this line into

"Other .htaccess content:
If you want anything else in your .htaccess, write it here and it'll be placed near the top."

You find this option in the admin panel under "Settings/SEO".


The explanation for this astounding effect is real simple:

All the modern browsers can handle the gzip compression but it is OFF on default.
You told the browsers with this code line that they should use the compression.
So the page is first compressed on the server, then transfered over the net and then the browser decompress it.

One can examine if the gzip-compression works on the following page:

http://www.gidnetwork.com/tools/gzip-test.php


This page told me that my page has a size of 23,709kb uncompressed and with compression ON there are only 4,941kb which are transfered over the net.
The google home page per example is a compressed page too.

I hear at first about gzip compression as YSlow give me this tip:
https://addons.mozilla.org/de/firefox/addon/5369/
(a firefox extension to analyze your page loading)


And here is my feature suggestion:

Isn`t it a nice idea if this simple way to accelerate your web page is ON in default in WSN Links?




Paul
developer

Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California

Total Topics: 61
Total Comments: 7868
Paul
Posted Aug 26, 2010 - 8:39 AM:

There used to be an option in WSN Links to select to gzip it script-side, but it kills your site if it's being done at the apache level already, plus it caused a few other difficult errors.

The .htaccess directive would do it at the apache level I guess. But almost every configuration value like that ends up breaking some people's websites when they have a different server configuration -- or perhaps a different web server entirely (tinyhttp, lightspeed, Windows ISAPI_Rewrite). So my inclination is to not break people's sites unnecessarily.
Search thread for
Download thread as
  • 0/5
  • 1
  • 2
  • 3
  • 4
  • 5



Sorry, you don't have permission to post posts. Log in, or register if you haven't yet.