A sampled image response declared a Content-Length above 1 MiB
ShipReady found a sampled image response with a declared Content-Length greater than 1,048,576 bytes.
Why it matters
A declared image transfer size above the scanner threshold is a concrete asset-review signal.
How ShipReady detects it
What it inspects
ShipReady collects distinct HTTP(S) img src URLs from fetched pages and reads streamed response headers without downloading image bodies.
What triggers a finding
It triggers when a safe image URL returns HTTP 200 with Content-Length strictly above 1 MiB.
What the evidence shows
The evidence proves the sampled response declared that byte count during the scan.
Limits of this check
Only the first five candidates are probed. Small images with both declared dimensions at or below 64 pixels, non-HTTP(S) sources, and srcset-only images are excluded; at most three findings are reported.
Missing lengths, safe-URL refusals, request failures, 408/429/5xx responses, and budget exhaustion are unmeasured or incomplete. ShipReady does not render, measure LCP, determine display size, or prove user impact.
How to fix it
Review the observed evidence
Review asset format and delivered variants for the layouts that use the image.
How to verify the change
Verify the intended behavior
Check the deployed asset headers and rendered selection after the change.
Expected: The reviewed asset meets the product’s intended transfer-size budget.