7 comments

• 

  Max

  2 years ago

  Thanks! It worked just fine for me
  reply
• 

  Dustin

  1 year ago

  "What does this mean for your users? Faster loading websites and less latency."
  
  Just wanted to note that this really depends - while the file will obviously transfer faster, being much smaller in size and taking less bandwidth, often it will actually take longer for the page to load as the content must be decompressed after transfer. More info is available on php.net.
  reply
• 

  Andreas

  1 year ago

  Thanks!
  
  Damn this is good.
  
  It reduced the page size from 9 k to 2 k.
  reply
• 

  Svi Poslovi

  1 year ago

  ob_start(”ob_gzhandler”);
  
  This doesn't work for me.
  
  And, Andreas, having in mind what Dustin wrote and the fact that, as well as decompression, compression also takes time, you should really compress everything. For instance, I have a 4 kB dynamic page. Sure I am not going to compress it. What's the purpose? It's not going to load faster...
  reply
• 

  Svi Poslovi

  1 year ago

  I don't see my previous comment but I suppose it will pop out eventually. Anyway, I have a minor addition to it. The first recommendation (with .htaccess) works for me, the second doesn't. I had to point this out because someone may think my VPS is incapable of doing any compression.
  
  The point of avoiding .htaccess in my case is that I don't wish to compress everything. I want just one include in the PHP file I wish to compress and nothing in others...
  reply
• 

  vishal

  1 year ago

  @Dustin :
  
  You probably have not been through details.
  
  Unless you have computer of 1970s, decompressing wont take any time (i mean negligible). But bandwidth and network technology can't compete with the CPU power.
  
  Conclusion:
  Its always better to use gzip, unless you expect very old version browsers to be used.
  reply
• 

  kareti

  1 year ago

  i got 500 internal server error after applying the code.
  dont know why!
  any thoughts??
  reply