{
  "acceptance": "The reconciled report states the byte definition and compression conditions, and a reader can reproduce the comparison from retained headers and field definitions. It does not translate bandwidth directly into people.",
  "automated_checks": true,
  "batch_id": "analytics-editorial-20261104-v1",
  "built_at": "2026-11-04T11:50:28.566595+00:00",
  "claims": [
    {
      "id": "c1",
      "section": "Explanation and verification steps",
      "source_numbers": [
        2
      ],
      "statement": "With Content-Encoding, metadata such as Content-Length normally refers to the encoded representation."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Encoding is negotiated using request and response headers, with Vary informing caches of the representation choice."
    }
  ],
  "description": "Name the byte field and compression layer before attributing a bandwidth change to crawler activity.",
  "diagram": [
    "Accept-Encoding: client capability",
    "Content-Encoding: selected representation",
    "Length: identify the encoded size",
    "Trend: compare the same byte field"
  ],
  "draft_hash": "b1922156281cc791191598cdf19dd68e136421fb4e7ba1df94f3923102869d8e",
  "evidence": {
    "observed_at": "2026-11-02T18:15:34.216949+00:00",
    "period": {
      "end": "2026-11-02T18:15:34.216949+00:00",
      "start": "2026-11-02T18:15:34.216949+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "Official documentation; no customer or own-site traffic measurement"
  },
  "evidence_kind": "documentation",
  "figure_caption": "Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.",
  "figure_kind": "comparison",
  "figure_notes": [
    "Record the encodings the client accepts.",
    "Inspect the encoding actually chosen for the response.",
    "Do not compare encoded and decoded sizes as one field.",
    "Keep units, representation and request conditions consistent."
  ],
  "figure_title": "Compare response bytes without mixing encoded and decoded sizes",
  "group": "Collection diagnostics",
  "human_review_claim": false,
  "intent": "compressed-response-byte-metrics",
  "interpretation": "MDN states that when Content-Encoding is present, metadata such as Content-Length describes the encoded representation unless explicitly specified otherwise. Its compression guide explains the negotiation between Accept-Encoding, Content-Encoding and Vary. Two tools can therefore report different byte totals for the same resource while measuring different quantities. Before investigating an apparent crawler bandwidth change, write down the definition of each byte field and the layer that supplied it.",
  "keyword_volume": "Not obtained",
  "limits": "A smaller response can reflect content or encoding changes. This guide supplies a comparison method, not a measured performance improvement or a universal expected compression ratio.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/compressed-response-byte-metrics/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A report compares compressed transfer bytes with decoded resource sizes and attributes the difference to traffic growth.",
  "product": "/ai-analytics",
  "published_at": "2026-11-04T12:00:11.476325+00:00",
  "reader": "Site owners and analysts investigating a report compares compressed transfer bytes with decoded resource sizes and attributes the difference to traffic growth.",
  "related": [
    "origin-logs-cdn-coverage"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/origin-logs-cdn-coverage/",
      "title": "Explain the cache blind spot in origin-only logs"
    }
  ],
  "research_document_ids": [
    "7669911eb3a448d3ae1227ebecf620cd",
    "8586f73d5a6dae2d31911ae88c16ed64"
  ],
  "slug": "compressed-response-byte-metrics",
  "source_signature": "7e0b7637e37871096a8de56ce199452667d2faa4e94df90161eaafeaeb7ba6ca",
  "sources": [
    {
      "hash": "d0cd3c5f42f14692709a2c9f0d77aa1a209ad88c700cfb7e60ae5da3e9ae51c8",
      "locator": "End-to-end compression / b14",
      "observed_at": "2026-11-02T18:15:34.216949+00:00",
      "title": "Compression in HTTP",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Compression"
    },
    {
      "hash": "c33afeca238b8cf2fcb8449127b75500ea0bd11c78eaeec77c1b40f537c7818c",
      "locator": "Content-Encoding header / b5",
      "observed_at": "2026-11-03T23:15:54.097500+00:00",
      "title": "Content-Encoding header",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Encoding"
    }
  ],
  "sources_required": [],
  "steps": [
    "Select one public test resource and retain its response headers, encoding negotiation and the byte fields displayed by each tool. Specify whether units are bytes, decimal KB or another unit.",
    "Create a field dictionary naming encoded body size, decoded size and any transport-overhead metric separately. Mark undocumented fields as unknown rather than treating them as equivalent.",
    "Compare requests with the same URL representation, time window and accepted encoding. Check Vary when different encoded responses can be cached.",
    "Recalculate the trend using one consistent field. Keep any compression change as a separate explanatory annotation and verify the request-count trend independently."
  ],
  "title": "Compare response bytes without mixing encoded and decoded sizes",
  "worked_example": "Hypothetical example: an application generates a 10 KB text representation that is delivered as a 3 KB encoded body. Comparing the application size with the transfer size produces a difference without any additional visits. Those numbers are illustrative, not an assumed compression ratio. If a proxy changes encoding, repeat the same request conditions and compare the same field on both sides of the change."
}