Skip to content
Klacos
Lire en français Early access
Menu
Protection Bot managementWeb application firewallRate limitingVerified botsAI crawler controlAccess rulesSSL/TLS certificatesExplained decisions
Performance Caching and purgeRules and redirectsLoad balancingWaiting roomService continuityCompression and HTTP/3
Analytics Traffic analysisCookieless analyticsGoals and funnelsTag managerLogs and exportsSharing and teams
Solutions Online shopsSaaS and APIsMedia and publishersAgencies and hosts
On-premiseHow it works Request early access
Compression and HTTP/3

Brotli compression and HTTP/3: lighter pages, without touching your server

Every unnecessary byte delays the page, especially on a phone over a mobile connection. And turning on Brotli or HTTP/3 on a server means a module, an upgrade and testing. Klacos compresses every response on the way through and serves it over the most recent protocol the browser supports. Your server has nothing to configure.

Request early access Talk to the team
Illustration: blocks and modules stacked on a base.
The problem

Pages heavier than they need to be

Plenty of servers send their pages, stylesheets and scripts uncompressed, or in an older format. Modern protocols, which use fewer connections and cope better with patchy networks, often stay switched off because nobody has time to upgrade the server.

Meanwhile, the visitor waits for the bytes to arrive. On a mobile connection the difference shows, and visitors who wait too long leave. Those extra bytes cost bandwidth, too.

Illustration: an hourglass mounted in a metal frame.
No setup

What your server no longer has to do

The service in front of your site takes care of it: each response is compressed on the way through, and each visitor gets the most recent format and protocol their browser supports. Older browsers still get Gzip over HTTP/1.1.

If your server already compresses its responses, Klacos works with that and recompresses where needed, with a limit that rejects abnormally bloated responses. Every connection is encrypted with certificates issued and renewed automatically, and your most requested pages never even reach your server, thanks to caching.

Illustration: a server rack surrounded by devices and dials.
What you get

Fewer bytes, more modern connections

Gzip, Brotli, Zstandard

The format is chosen per visitor, based on what their browser accepts.

HTTP/2 and HTTP/3

Modern protocols for browsers that speak them, HTTP/1.1 for the rest.

WebSocket

Your real-time apps go through the same service, with no separate setup.

Static files

Files served directly by the service, without going through your server.

Compression and protocols are part of your site’s performance and availability.

Questions

Questions about compression and protocols

Do I need to enable Brotli on my server?

No. Compression is handled by the service in front of your site. Your server can keep sending its responses as they are.

Are my images optimised?

No. Responses are compressed where it helps, but images aren’t resized or converted.

Are older browsers still served?

Yes. Each visitor gets the format and protocol their browser understands, all the way down to HTTP/1.1 and Gzip.

Opening early 2027

Lighter pages from day one

Request early access, or tell us what serves your site today.

Request early access Talk to the team