What is Accept-Encoding?

Accept-Encoding tells a server which compression or content-coding methods the client can process.

What can it tell you?

Values such as gzip, br, or zstd indicate acceptable encodings that a server may use to reduce response size.

How NetKarte shows it

Read Accept-Encoding under Client headers in the HTTP information card. No input is needed: the received value appears automatically. Check both the encoding names and any q weights. It lists acceptable candidates, not necessarily the encoding used for the actual response.

Notes

A reverse proxy or CDN may compress responses between the browser and application. This value alone does not determine traffic volume or speed.

Why gzip or br does not prove compression

gzip, br lists acceptable encodings, not the encoding used for this response. A server may leave a small response or an already compressed image uncompressed.

With weights, gzip;q=0 rejects gzip. Omitting q means 1; identity means no such transformation. Read the weight as well as the token.

Check the actual response

Select the relevant request in browser developer tools and inspect the response Content-Encoding. NetKarte's Accept-Encoding display cannot replace that response header.

For performance questions, examine size and timing separately. The presence of a compression format is not a diagnosis of connection speed.