references/support-topics/fast-data-transfer-payloads.md

GitHub
idfast-data-transfer-payloads
titleFast Data Transfer payloads
statusactive
candidateKinds["uncached_route"]
frameworks["*"]
priority65
citations["https://vercel.com/docs/manage-cdn-usage","https://vercel.com/docs/caching/cdn-cache"]
maxBriefChars900

Investigation Brief

When uncached routes carry high bandwidth, check payload shape before recommending only cache headers. Fast Data Transfer includes the bytes transferred by requests and responses; compare compressed response sizes to the signal, not raw JSON.

Evidence To Check

Use bandwidthByCache, response size, and source serialization. Look for unbounded JSON, large embedded objects, static files through functions, missing pagination.

Do Not Recommend When

Do not shrink payloads without identifying fields or assets that are unnecessary for the route’s response.

Verification

Tie the finding to observed bytes, cache result mix, and the exact response line. A "large payload" claim must reflect post-compression bytes — the unit FDT meters.