But that is not recommended.
One has to realise that the real problem here Pingdom is, not Cloudflare. The problem roots from them and therefore shall not be concealed at Cloudflare’s end.
@enovato if you really care about a fast and good ranking site you definitely do not run Pingdom on it There are so many good benchmark tools which work properly and have been maintained in the last 5 years - unlike Pingdom.
Here are some little examples, why Pingdom must be the problem, and why it is not Cloudflare’s fault.
curl -sI https://code103.hotmann.de/app.min.css | grep "content-encoding"
curl -H "Accept-Encoding: gzip" -sI https://code103.hotmann.de/app.min.css | grep "content-encoding"
curl -H "Accept-Encoding: br" -sI https://code103.hotmann.de/app.min.css | grep "content-encoding"
So Cloudflare serves every user according to what he is capable of handling. If your browser does not state that he can use brotli, he will not be served brotli.
If a client signals that he can handle multiple encoding-types, then he will be served the best one.
So what happened here is, that if a client sends a request like:
curl -H "Accept-Encoding: gzip, br" -sI https://code103.hotmann.de/app.min.css | grep "content-encoding"
he mostly will be served:
As Brotli is superior in basically all text-based compressions.
So if Pingdom runs benchmarks with
br in their
"Accept-Encoding" header, then yes… ofc they will be served according to what they say they can handle.
Beside that (I know, everyone says that) you should not focus on benchmarks too much, but just as much as they are reasonable. Not using modern technique is definitely not reasonable!
Have a quick search about “brotli vs gzip” and decide yourself, what you want to stick with. Very likely you want to have brotli enabled always, and gzip as fallback.
So here my advice:
- stop using Pingdom, it really is a bad tool. (@fritex already mentioned really good tools)
- go with what makes your site measurable fast, not what makes it look better on paper. As Pingdom does not tell you why not using gzip is bad, you really shall ignore such misleading statements.
- leave brotli enabled at Cloudflares - it greatly speeds up your site.
- note that Cloudflare does not use gzip and brotli at their best settings. Guess it was:
4.1. Brotli lvl. 6
4.2. gzip lvl. 4
(could be wrong - don’t quote me on this)
So if you want to get the very best out of it, you need to do it on your own. then you can go for brotli lvl 11 (extreme compression) and gzip lvl 9 (best for gzip).
Note that this really can be worth it, but now you need to turn off compression at Cloudflare, as Cloudflare otherwise would re-compress it at its own settings.