Posted: February 23rd, 2010 | Filed under: IIS & HTTP, Performance Tools | Tags: css compression, deflate, gzip, html compression, http compression, httpzip, iis compression, server compression, zipenable
HTTP compression on IIS is easy to enable with tools such as httpZip or ZipEnable and requires no client-side configuration to obtain benefits, making it a very smart way to get extra performance and a better user experience.
It’s well known that there is a limited amount of bandwidth on most Internet connections and anything IT administrators can do to accelerate site load time benefits not only the organization, but users as well. HTTP compression, a function built into both browsers and servers, can substantially improve site performance by reducing the amount of time required to transfer data between the server and the client. When data is encoded using a compressed format like GZip or Deflate, it introduces complexity into the HTTP request/response interaction by necessitating a type of content negotiation. This content negotiation communicates with the browser, deciding if it can or cannot handle the compressed data and sends the appropriate version of the resource to the browser.
Read the rest of this entry »
No Comments »
Posted: August 17th, 2009 | Filed under: IIS & HTTP, Performance Tools, Web Design, Development, & Usability | Tags: deflate, gzip, http compression, httpzip, zipenable
What is HTTP compression and how does it work?
HTTP compression is a long-established Web standard in which a GZip or Deflate encoding method is applied to the payload of an HTTP response, significantly compressing the resource before it is transported across the Web.
When data is encoded using a compressed format like GZip or Deflate, it introduces complexity into the HTTP request/response interaction by necessitating a type of content negotiation. Whenever compression is applied, it creates two versions of a resource: Read the rest of this entry »
No Comments »
Posted: April 24th, 2009 | Filed under: Browsers, Web Design, Development, & Usability | Tags: ajax cache, cache, caching, data uri, gzip, multipart stream, page speed, request bundling, site performance, web 2.0
Yesterday we saw an interesting effort from Digg to address the problem of multiple requests and its effect on page speed.
Recently there has been growing interest in various schemes for request bundling. For example, a way to use data URIs in most browsers was shown here: http://www.hedgerwow.com/360/dhtml/base64-image/code.txt. It is ugly, but mostly works. In the past we have seen other folks use a variety of client and server-side schemes to bring inlined images and other assets to the masses - mostly with little success. That’s too bad. Read the rest of this entry »
3 Comments »
