HTML Document Size
Checks that the initial HTML payload is under 1MB.
What this check measures
We measure the raw HTML response size. Over 1MB is flagged — usually the result of massive inline JSON, SSR'd server state, or embedded images as data URIs.
Why it matters
Large HTML slows TTFB and parsing. On mobile, every extra 100KB of HTML adds ~200ms to first paint. Better: ship minimal HTML and fetch data client-side.
How our audit detects it
Measure size of the raw HTML response body. Flag over 1 MB.
Typical findings
- error_outline2MB+ HTML because SSR dumps all CMS data inline.
- error_outlineBase64-encoded images in HTML instead of <img src>.
How to fix
Move large JSON to separate API endpoints (fetched client-side after first paint). Use img tags with src URLs, not data: URIs. Minify HTML if not already.
Frequently asked questions
Is server-state hydration the problem?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
SSR / Pre-rendering
Checks if the page is server-rendered or statically pre-rendered.
TechnicalHTTP Status Codes
Checks that pages return proper status codes — 200 for live, 404 for missing, 301 for moved.
TechnicalNo Client-Side Redirects
Checks that redirects happen server-side, not via JavaScript.
TechnicalViewport Meta Tag
Checks for <meta name="viewport" content="width=device-width, initial-scale=1">.