Compression and Why Pages Transfer Faster

What is happening

Before sending a file, the server compresses it. The browser receives the smaller version and expands it back. Nothing about the page changes; only the amount of data crossing the network does.

It works so well on text because text is repetitive. HTML, stylesheets, and scripts contain the same tags, property names, and words over and over, which is exactly what compression exploits. Reductions of seventy percent or more are ordinary.

Two methods are in common use. The older one is universally supported; the newer one compresses better and is supported by every current browser. Most hosting offers both and picks whichever the browser accepts.

What compresses and what does not

That table explains a common confusion. Turning on compression does not reduce your image weight at all, so a site whose problem is oversized photographs will see almost no improvement from it.

Compression handles the code; resizing handles the images. They are separate problems with separate fixes.

Checking whether yours is on

Two ways, both quick.

Open the browser developer tools, go to the network tab, reload the page, and look at an HTML or CSS file. It will show both the transferred size and the actual size. If those differ substantially, compression is working. If they are identical, it is not.

Alternatively any speed testing tool will flag uncompressed text resources directly, usually as one of the first recommendations.

The check takes a minute and is worth doing once, because when compression is off nothing about the site looks wrong. It is simply slower than it needs to be, invisibly.

Turning it on

On most modern hosting it is already enabled and there is nothing to do.

Where it is not, the options are a setting in the hosting control panel, a line in the site's configuration file, or a caching plugin that handles it. Which applies depends on the setup, and the host's support can usually enable it in minutes.

Where a content delivery network sits in front of the site, compression may be handled there instead, which is equally fine and worth confirming rather than assuming.

Minification, which is different

Frequently conflated with compression and a separate thing.

Minification removes what a file does not need: whitespace, comments, and long variable names. It is done once, to the file itself, before it is served. Compression happens in transit, every time, and is undone by the browser.

They stack. A minified file compresses further, and doing both is standard practice. Minification is the one with a risk attached, since a badly minified script can break, which is why it belongs on a staging copy first.

What it is worth

On a typical small business site, the text files might total two hundred kilobytes uncompressed and sixty compressed.

That saving is modest on a fast connection and meaningful on a poor mobile one, where it can be several hundred milliseconds. It also arrives before anything else, since HTML has to be received before the browser can discover what else to load.

So it is a small absolute saving at the most valuable point in the sequence, which is a reasonable return for a setting rather than a project.

Where the actual weight is

Worth ending on, because compression is frequently presented as a speed fix and it is a small one.

On most small business sites images are eighty percent or more of the page weight, and compression does nothing for them. A site with three uncompressed photographs at two megabytes each has a problem that no server setting will address.

The order that makes sense: resize and compress the images, remove scripts nobody uses, confirm text compression is on, then look at the server response. Compression belongs in that list and not at the top of it, which is the same prioritisation as in hosting and its effect on speed.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.