Page Size Checker
Paste a page\u2019s HTML and instantly see total weight, breakdown by content type (HTML, scripts, styles, images), and Core Web Vitals implications. Fast pages rank higher and convert more — knowing your weight is step one.
Paste HTML
How to use the Page Size Checker
View source of the page you want to measure, copy the HTML, paste it into the input. The tool calculates total raw HTML weight, breaks it down by inline JavaScript, inline CSS, content, and inline base64 images, and counts external resource references (scripts, stylesheets, images, preloaded fonts).
Why this tool matters
Page weight is one of the strongest predictors of bounce rate and Core Web Vitals. Pages above 1.5 MB raw HTML weight regularly fail Largest Contentful Paint thresholds. Inline JavaScript and CSS bloat the initial HTML and delay First Contentful Paint. Knowing your weight breakdown tells you exactly where to cut.
Common use cases
- Pre-launch performance audit of a landing page
- Diagnosing why a page fails Core Web Vitals despite a fast server
- Comparing your page weight to a competitor\u2019s
- Identifying excessive inline scripts vs. external scripts
- Finding base64-encoded images that should be served as separate files
- Building a performance budget for your team
Raw HTML vs. total page weight
Our tool measures the raw HTML that your server delivers. The total downloaded weight of the page (including all linked scripts, images, fonts, stylesheets) is usually 5-15× larger. For full page-weight measurement use Chrome DevTools Network tab or WebPageTest. The raw HTML weight is the right metric for: server-response performance, mobile data-cost concerns, and inline-bloat detection.
Frequently Asked Questions
What is a “good” raw HTML weight?
Under 100 KB is excellent. 100-500 KB is healthy. 500 KB – 1.5 MB is heavy. Above 1.5 MB starts to fail Core Web Vitals reliably on slow connections.
Should I inline scripts and CSS?
Critical above-the-fold CSS — yes, inline it for fastest first paint. Below-the-fold CSS and scripts — load externally, ideally deferred or async. Inlining everything bloats every page request and prevents browser caching.
Why does my page seem fast even with high weight?
Modern compression (Brotli, gzip) reduces transmitted bytes by 60-80%. A 1 MB raw HTML page may only transmit 200 KB. Compression hides weight issues until you hit slow networks where decompression cost compounds.
How does this relate to Largest Contentful Paint (LCP)?
LCP measures when the largest visible element finishes rendering. Heavy inline scripts block rendering and inflate LCP. Heavy inline base64 images delay LCP because the browser must decode them before painting.
Want a full Core Web Vitals audit with prioritized fix recommendations?
Riman Agency runs performance and Core Web Vitals optimization programs.
