zstd not recognized as compression (new in M123)

FAQ

[X] Yes, my issue is not about variability or throttling.
[X] Yes, my issue is not about a specific accessibility audit (file with axe-core instead).

URL

https://liberda.nl/weblog/trust-no-client/

What happened?

"Enable text compression" diagnostic appeared for the document

Enable text compression: Potential savings of 21 KiB.
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. [Learn more about text compression](https://developer.chrome.com/docs/lighthouse/performance/uses-text-compression/).

What did you expect?

recognizing zstd as a compression algorithm (it has shipped in M123)

What have you tried?

checked logs (reduced for clarity):

{
  "method": "Network.responseReceived",
  "params": {
    "type": "Document",
    "response": {
      "url": "https://liberda.nl/weblog/trust-no-client/",
      "status": 200,
      "statusText": "",
      "headers": {
        "content-encoding": "zstd",
        "content-length": "8155",
        "content-type": "text/html",
        "vary": "Accept-Encoding"
      },
      "responseTime": 1711224797711.976,
      "protocol": "h2",
    },
  }
}

How were you running Lighthouse?

CLI

Lighthouse Version

b64619a836035d1cffa864f98fbd21457e6515be

Chrome Version

123.0.6312.58

Node Version

v21.7.1

OS

Alpine Linux

Relevant log output

No response

GoogleChrome / lighthouse