A sampled script response exceeded ShipReady’s bounded size threshold
ShipReady found a sampled script response above 512,000 bytes when compressed or 1,600,000 bytes when uncompressed.
Why it matters
A declared script size can guide bundle review, while runtime execution cost needs separate tooling.
How ShipReady detects it
What it inspects
ShipReady collects distinct HTTP(S) script src URLs and reads response headers without downloading script bodies; missing lengths receive one identity-encoding header probe.
What triggers a finding
It triggers for a safe HTTP 200 response above 512,000 compressed bytes or 1,600,000 verified uncompressed bytes.
What the evidence shows
The evidence proves the sampled response declared the shown size and encoding basis during the scan.
Limits of this check
Only the first three candidates are probed and at most two largest findings are reported. Unsafe URLs, failures, 408/429/5xx responses, missing lengths, and budget exhaustion do not establish a small bundle.
ShipReady does not download, parse, execute, profile, or attribute bundle contents, and does not measure INP, TBT, user experience, rankings, or root cause.
How to fix it
Review the observed evidence
Use bundle analysis and route-loading design to identify code that can be reduced, split, or deferred.
How to verify the change
Verify the intended behavior
Inspect the deployed script response and application behavior after a change.
Expected: Reviewed script responses meet the chosen transfer-size budget.