Brotli Checker

About Brotli Checker

Brotli Checker requests a page while advertising that it accepts br, gzip and deflate, then reports which content encoding the server actually chose. Brotli typically compresses text assets noticeably better than gzip, so this confirms whether your server or CDN is delivering the smaller format.

How to use it

1. Enter the full address of a page or asset in the URL box, for example https://example.com. https:// is added when missing.
2. Press Check Brotli. Our server sends a GET request with an Accept-Encoding header of br, gzip, deflate.
3. Read the banner: Brotli compression enabled, or Brotli not supported. The badge shows the encoding returned.
4. Check the Encoding, HTTP Status and Server rows for context on what answered.

What the request advertises

https://example.com

Sent header: Accept-Encoding: br, gzip, deflate. A server that compresses with Brotli replies content-encoding: br and the tool reports enabled. A gzip reply is reported as not supported, with gzip shown as the encoding.

When to use it

• Checking that a CDN setting for Brotli took effect on your HTML pages.
• Diagnosing why a site serves gzip when the hosting plan promises Brotli.
• Testing a specific JavaScript or CSS file address to see how it is compressed.
• Confirming compression is active before you run a page speed audit.

Questions about Brotli Checker

Why does it say not supported when my server has Brotli installed?

The check reads the content-encoding of that single response. Servers often skip compression for tiny files, images, already compressed types or requests they consider unsafe. Test an HTML or JavaScript file address for a fair result.

What does an encoding of none mean?

The server sent the response without any compression. That is expected for images and video, but for text it means compression is off or the response was under the server's minimum size.

Do redirects affect the result?

Yes. Up to 10 redirects are followed, and the encoding reported is from the final response, not the first. Each hop is checked against the public-host rule.

Is the whole page downloaded?

No. Only the headers are examined, and the body is cancelled immediately so large pages are never buffered. The request is made by our server, so the URL is sent to it.

Why does the request use a custom user agent?

It identifies itself as MaffeiTools so site owners can recognize the traffic. Some firewalls treat unknown agents differently, which can change the compression a server chooses.

Related tools

• HTTP/2 CheckerCheck if a website supports HTTP/2
• Website Hosting CheckerCheck where a website is hosted
• IP LookupLook up information about an IP address
• DNS LookupLook up DNS records for a domain
• WHOIS LookupLook up WHOIS information for a domain
• PingPing a domain or IP address