Turn a Per-Response Compression Difference Into Monthly Bandwidth

How to Use This Tool

Multiply compressed-size differences by request volume rather than comparing percentages alone. Calculate monthly transfer saved by Brotli versus gzip from response sizes, request volume and cache miss rate.

The failure Compression Savings is designed to catch

Five kilobytes matters more than five percentage points when multiplied across a high-volume origin workload. The boundary is the job stated in Turn a Per-Response Compression Difference Into Monthly Bandwidth; Compression Savings is not intended to score or transform a different workflow.

The Compression Savings input contract

The fields used for this specific operation are Uncompressed response KB, Gzip response KB, Brotli response KB, Monthly origin responses. Keep the source values beside the Compression Savings result, because replacing the original would remove the evidence needed to reproduce or reverse the operation.

• For Compression Savings, Uncompressed response KB starts at 1000 in the worked case; replace that example with the matching source value.
• For Compression Savings, Gzip response KB starts at 300 in the worked case; replace that example with the matching source value.
• For Compression Savings, Brotli response KB starts at 250 in the worked case; replace that example with the matching source value.
• For Compression Savings, Monthly origin responses starts at 100000 in the worked case; replace that example with the matching source value.

Worked result for Compression Savings

The executable case called Default decision scenario expects out: 5.0 GB. Verify that observation before entering real material, and then change one Compression Savings field at a time so an unexpected direction or formatting change can be traced to a specific input.

Reading the Compression Savings output

It combines uncompressed response kb, gzip response kb, brotli response kb and monthly origin responses into one decision result using the formula explained on the page. Apply that answer only when Uncompressed response KB, Gzip response KB, Brotli response KB, Monthly origin responses describe the same scope and format as the worked operation. If the source uses different units, quoting, nesting, timing or account rules, a plausible-looking Compression Savings output is not sufficient validation.

Assumptions attached to Compression Savings

• Compression Savings assumes that all inputs describe the same unit or reporting period unless the field explicitly says otherwise.
• Compression Savings assumes that the model includes only the four visible inputs and does not infer hidden platform charges.

If one of these Compression Savings assumptions is false, keep the result as a diagnostic rather than production or decision data, and choose an implementation that explicitly supports the missing rule.

Evidence maintained for Compression Savings

The recorded reference is MDN Web Docs — HTTP. Reopen that source when the definition, format, fee or policy behind Compression Savings changes; private configuration and downstream acceptance still have to be checked in the user's own system.

Where Compression Savings runs

The named operation executes in browser JavaScript without an ecech calculation API. For Compression Savings, local execution reduces transmission but does not control browser extensions, device security or the destination where the result is pasted, so sensitive inputs still require the user's normal handling rules.