Gzip Brotli Compression Singapore: How to Switch It On Safely

Quick answer: Gzip brotli compression Singapore sites rely on means your server shrinks HTML, CSS and JavaScript files before sending them, so browsers download far fewer bytes. Brotli compresses text roughly fifteen to twenty per cent smaller than gzip, and most modern hosting can enable either in minutes.

There is a category of speed problem that costs nothing to fix and takes about ten minutes, and text compression is the clearest example of it. When someone in Tampines opens your site on mobile data, their browser has to pull down every HTML, CSS and JavaScript file your pages depend on. Those files are plain text, and plain text is extremely repetitive, which means it squashes down beautifully. Gzip and brotli are the two compression formats that do the squashing, and both are supported by essentially every browser your Singapore visitors will use. Yet when we run technical audits, uncompressed or partially compressed text assets still show up regularly, usually on sites where a developer set things up years ago and nobody has looked since. The frustrating part is that this is not a design trade-off or a difficult engineering decision. Nothing about your site changes visually. You are simply choosing whether to send 240KB or 60KB down the wire for the same result. This guide explains what each format does, how to check what your server is currently serving, and how to switch things on across the hosting stacks Singapore SMEs actually use, as part of a broader technical SEO approach.

What Text Compression Actually Does To Your Files

Compression works by finding repetition and replacing it with shorter references. A CSS file might contain the string “background-color” two hundred times, and a JavaScript bundle might repeat the same function names and syntax patterns thousands of times over. Rather than transmit every one of those characters, the compression algorithm builds a lookup of repeated sequences and sends a much shorter coded version. The browser decompresses it on arrival, in a few milliseconds, and works with the original file exactly as written. Nothing is lost. This is what engineers mean by lossless compression, as distinct from image compression, where quality genuinely is traded away for file size.

The practical effect on a typical Singapore small business site is significant. A WordPress theme with a page builder often ships 300KB to 600KB of CSS and JavaScript before any compression is applied. Compressed with gzip, that commonly drops to somewhere between a fifth and a third of the original size. Compressed with brotli, it drops further still. For a visitor on stable home fibre in a Punggol HDB flat, that difference might cost a couple of hundred milliseconds. For the same visitor standing on an MRT platform with two bars of signal and a congested cell, it is frequently the difference between a page that renders in under two seconds and one that hangs long enough for them to hit back.

Compression applies to text formats only. HTML, CSS, JavaScript, JSON, SVG and XML all compress well. JPEG, PNG, WebP, MP4 and PDF files are already compressed internally, and running them through gzip again achieves almost nothing while wasting server processing time. A properly configured server knows the difference and only compresses what benefits, which is why the file type list in your server configuration matters as much as switching the feature on in the first place.

The exchange itself is negotiated automatically. Your visitor’s browser sends a header announcing which compression formats it can accept, and your server picks the best one both sides support and returns the file along with a header stating what it used. There is no cookie, no plugin behaviour, and no user-facing setting. If your server never advertises compression, the browser simply receives the full uncompressed file and no error is raised anywhere. That silence is exactly why the problem persists on so many sites for so long.

Gzip Versus Brotli: The Honest Comparison

Gzip has been around since the early 1990s and is supported universally. Brotli was released by Google in 2015, is now supported by every current browser, and generally produces smaller output on text. The temptation is to treat this as a simple upgrade decision, but there are trade-offs worth understanding before you flip anything.

The nuance most guides skip is that brotli has eleven compression levels, and the highest ones are computationally expensive. Compressing a large JavaScript bundle at brotli level 11 can take noticeably longer than gzip, which is irrelevant if you do it once and cache the result, but genuinely harmful if your server does it fresh on every single request during a traffic spike. The sensible default is brotli at a moderate level for dynamic HTML and brotli at maximum level for static files that are compressed once and stored. Most managed hosting and CDN platforms already do exactly this, which is another reason the practical answer for most Singapore SMEs is to enable both and let the negotiation sort itself out.

We are also going to push back on a piece of advice that circulates widely in Singapore business owner groups: the idea that switching from gzip to brotli is a meaningful speed project on its own. Conventional wisdom treats it as a headline optimisation, and it is not. Moving from no compression to gzip is a large win. Moving from gzip to brotli is a real but modest refinement, often worth 30KB to 80KB on a typical page. Worth doing, certainly, and free, but it will not rescue a site whose actual problem is four unoptimised hero images and a bloated slider plugin. Prioritise in that order, and treat compression as the cheap foundation rather than the fix. That prioritisation logic is the same one we apply when scoping work for small business SEO clients.

How To Check What Your Site Is Serving Right Now

You do not need a paid tool for this. Open your site in Chrome, press F12 to open developer tools, click the Network tab, and reload the page. Click on the first entry in the list, which is your HTML document, and look at the response headers on the right. If you see a line reading content-encoding followed by br, you are being served brotli. If it says gzip, you are on gzip. If there is no content-encoding header at all, your text is being sent uncompressed.

Check more than the HTML document. Sort the network list by file type and inspect at least one CSS file, one JavaScript file, and any JSON responses your site loads. A pattern we see repeatedly is HTML compressed correctly by the server while static assets served from a subdomain or an older CDN configuration go out raw. The site passes a superficial check and still ships hundreds of unnecessary kilobytes on every visit.

The second thing to compare is the transferred size against the actual resource size. Chrome shows both in the network panel: the smaller number is what crossed the network, the larger is what the browser is working with. If those two numbers are identical for a CSS file, that file is not being compressed regardless of what any plugin dashboard claims. We treat this two-number comparison as the only trustworthy verification, because caching plugins routinely report compression as enabled while the server configuration overrides them.

For a repeatable check across many pages, run your site through PageSpeed Insights and look for the “Enable text compression” opportunity, which lists every uncompressed file with its potential saving in kilobytes. That report is the fastest way to hand a specific, actionable list to a developer. When we audit a site, this is one of the first checks we run, precisely because it is quick to verify and quick to remedy, and it establishes early whether the site has been maintained or simply left running. Our SEO consulting and audit work usually opens with exactly this class of check before anything more involved.

Enabling Compression On Common Singapore Hosting Setups

The right method depends entirely on your server software, and most Singapore SME sites sit on one of four arrangements.

Apache hosting, including most cPanel shared plans. Compression is handled by a module called mod_deflate for gzip, and mod_brotli where available. On cPanel there is usually a graphical option labelled Optimize Website that switches on compression for common text types without touching any files. If you are editing configuration directly, the rules go in your .htaccess file and specify which MIME types to compress. This is the setup behind a large share of the local shared hosting plans sold in Singapore, typically in the range of SGD 5 to SGD 20 per month.

LiteSpeed or OpenLiteSpeed hosting. Brotli support is built in and generally enabled by default, with settings exposed through the server admin console and, on WordPress, through the LiteSpeed Cache plugin. This is common on regional budget hosts and is usually the least work of any option, since the sensible defaults are already in place.

Nginx, typical on a VPS. Gzip is configured through a handful of directives in the server configuration file, and brotli requires a module that many distributions now include. A VPS from a regional provider suitable for a mid-sized Singapore business site typically runs SGD 15 to SGD 60 per month, and if you are paying for one, compression should be part of the initial build rather than an afterthought.

Behind a CDN such as Cloudflare. The CDN compresses at the edge regardless of what your origin server does, which is genuinely useful for sites on restrictive hosting. Cloudflare’s free tier applies brotli to eligible content automatically. The caveat is that compression at the edge only helps for requests the CDN actually serves, so anything bypassing the cache, including most logged-in and checkout traffic, still depends on your origin configuration. For Singapore online stores this matters more than people expect, because the pages where speed converts hardest are frequently the ones that bypass the edge cache. We cover that interaction in more detail in our work on e-commerce SEO.

Managed WordPress hosting handles all of this at the platform level, and if you are on such a plan the correct action is usually to verify rather than to configure. In our experience the most common failure on managed platforms is not absent compression but a caching plugin installed on top of the host’s own layer, with the two fighting over the same headers.

Where Compression Fits In A Realistic Speed Plan

Compression is a foundational fix, not a strategy. It reduces transfer size, which improves how quickly the browser can begin working, and that helps First Contentful Paint and Largest Contentful Paint in most cases. It does nothing whatsoever for a slow database query, a render-blocking third party script, or a layout that shifts because an image has no dimensions declared.

The order we recommend for a Singapore SME site is straightforward. Enable text compression first, because it is free, safe and immediate. Fix image weight and format second, because on most local business sites images account for the largest share of page weight by a wide margin. Address render-blocking scripts and unused CSS third, since that is where the real engineering effort lives. Consider a CDN fourth, which for a business serving only Singapore visitors matters less than the marketing suggests, given how short the physical distance already is.

That last point deserves emphasis because it is frequently sold the other way round. A cafe in Tiong Bahru serving customers within a few kilometres gains far less from global edge distribution than a business with genuine international traffic. The latency advantage of a CDN shrinks considerably when your server and your visitors are both already in Singapore or nearby. Compression, by contrast, helps every visitor on every connection regardless of geography, which is exactly why it belongs first in the queue. This is the kind of sequencing judgement that separates a useful speed plan from a shopping list, and it is something we work through with clients across the industries we serve.

A common way compression goes missing is not that it was never enabled, but that it was quietly removed. On shared cPanel hosting, a theme or plugin update can rewrite the .htaccess file and drop the compression directives, and nothing on the site looks different afterwards. Restoring the rules usually cuts the transfer weight of CSS and JavaScript substantially, with no change to the site’s appearance, code or functionality, which is why compression is worth re-checking after every major update.

In our law firm case study, the Month 1 technical audit lifted the mobile Lighthouse score from 52 to 81 through image compression, render-blocking JS deferral and font loading optimisation. None of those fixes was text compression, but the lesson is the same: some of the biggest speed gains come from basic delivery settings that were never configured or have drifted, so check them before paying for bigger infrastructure changes.

Our Take

Text compression is the cheapest speed work available to a Singapore business, and its main value is not the milliseconds it saves but the fact that its absence tells you something. A site shipping uncompressed JavaScript in 2026 is almost always a site nobody has technically reviewed in years, and where we find one such gap we typically find several. We recommend checking your content-encoding headers today, comparing transferred against resource size for at least three files, and enabling brotli where your host supports it. Then move on to images, which is where the genuinely large wins usually sit. Do not let a compression setting become the whole speed project, and do not assume a plugin dashboard reporting green is telling you the truth about what your server is actually sending. If you would like the full picture of what your site is transferring on every page load, our SEO services include this as standard, and our pricing page sets out how ongoing technical maintenance is structured.

Frequently Asked Questions

What is the difference between gzip and brotli compression?

Both shrink text files before they are sent to a browser, and both are lossless, meaning the file arrives identical to the original. Brotli is newer and typically produces files around fifteen to twenty per cent smaller than gzip on HTML, CSS and JavaScript. Gzip is faster to compress at default settings and is supported by older browsers. Most servers today can offer both and let the browser pick.

Will enabling compression break my website?

It is very unlikely. Compression happens in transit and the browser decompresses the file before using it, so your code, layout and functionality are unchanged. The rare problems come from double compression, where a plugin and the server both compress the same response, or from compressing file types that are already compressed. Enabling it through your host’s own control panel option avoids nearly all of these risks.

How much faster will my site get with brotli?

On a typical Singapore small business site, moving from no compression to gzip or brotli commonly reduces text transfer by 60 to 80 per cent, which on mobile data is usually worth a few hundred milliseconds. Moving from gzip to brotli is a smaller refinement, often 30KB to 80KB per page. Both are worth doing because they cost nothing, but neither will fix a site whose real problem is oversized images.

Does compression help my Core Web Vitals scores?

Indirectly, yes. Smaller files arrive sooner, so the browser can start parsing and rendering earlier, which usually improves First Contentful Paint and often Largest Contentful Paint. It has no effect on Cumulative Layout Shift, which is caused by elements moving during load, and little effect on Interaction to Next Paint, which is driven by JavaScript execution time rather than download size.

Do images need gzip compression too?

No. JPEG, PNG, WebP and GIF files are already compressed internally, and running them through gzip or brotli again produces almost no size reduction while consuming server processing time. The exception is SVG, which is a text format and compresses very well. Image weight is reduced instead by choosing modern formats, sizing images correctly, and using appropriate quality settings.

How do I check if my Singapore website already uses compression?

Open the site in Chrome, press F12, click the Network tab and reload. Select the main document and look for a content-encoding header in the response, which will read br for brotli or gzip. Also compare the transferred size against the resource size for a CSS or JavaScript file. If those two numbers are the same, that file is not compressed regardless of what your plugin dashboard says.

Does Cloudflare handle compression for me?

Cloudflare applies brotli at the edge for eligible content, including on its free plan, which helps a great deal on restrictive hosting. The limitation is that it only applies to requests Cloudflare actually serves. Traffic that bypasses the cache, including most logged-in sessions, cart pages and checkout flows, still depends on your origin server being configured correctly.

Is brotli supported by all browsers used in Singapore?

Every current version of Chrome, Safari, Firefox and Edge supports brotli over HTTPS, which covers essentially the entire Singapore market on both desktop and mobile. Browsers that do not support it simply do not request it, and the server falls back to gzip automatically. There is no scenario where enabling brotli leaves a visitor unable to load your site.

My host says compression is enabled but PageSpeed still flags it. Why?

Usually because compression is applied to HTML but not to static assets, or because some files are served from a subdomain or third party origin with its own configuration. Check each flagged file individually in the Network tab rather than trusting a single summary. Third party scripts you do not control will sometimes appear in this list and cannot be fixed from your end.

Should I pay for a plugin or service to manage compression?

Generally no. Compression is a server feature, and most hosting in Singapore, whether shared cPanel, LiteSpeed or a managed WordPress plan, exposes it either by default or through a single control panel toggle. Paid optimisation plugins bundle it alongside caching and asset minification, so you may end up with it as part of a wider tool, but compression alone is not worth a subscription.