Website Page Size Checker
Check the HTML page size of any URL and get a resource breakdown — images, scripts, stylesheets, and inline assets.
Did this tool work for you?
How to use this calculator
- 1
Enter the full URL of the page you want to analyse.
- 2
Click "Check Now" to fetch the page and measure its HTML size.
- 3
Results show the HTML document size, compression, and a count of referenced resources.
- 4
Note: this measures the HTML document only, not the total page weight including images and scripts.
Frequently asked questions
What is a good page size?
Google recommends keeping HTML document size under 100KB. Full page weight (HTML + CSS + JS + images) ideally under 1–2MB, though modern pages often exceed this. For mobile users, aim for under 500KB total page weight to minimize data costs and improve load times on slower connections.
What is the difference between HTML size and total page size?
HTML size is just the initial document returned by the server. Total page size includes all resources the HTML references: CSS files, JavaScript bundles, images, fonts, and API calls. This tool measures only the HTML document. Use Chrome DevTools Network tab or WebPageTest for full page weight.
Why does page size matter?
Larger pages take longer to download, parse, and render. This directly affects Core Web Vitals (Largest Contentful Paint, Total Blocking Time). Mobile users on slow networks are most affected. Search engines also have document size limits — extremely large pages may not be fully indexed.
What is content encoding (gzip/brotli)?
Web servers compress responses before sending them. Gzip reduces file size by 60–80%; Brotli achieves 10–25% better compression than gzip. If your server returns "content-encoding: gzip" or "br", compression is working. Without compression, your users download uncompressed files.
Website Page Size Checker — Analyse page weight and resources
Page size and SEO
Large HTML documents can slow crawling and indexing. Google's crawler has a document size limit (approximately 15MB) beyond which content may not be indexed. More practically, large pages signal poor code hygiene — bloated HTML from CMS plugins, unnecessary inline CSS, and duplicate content all inflate page size.
Optimizing page size
Minify HTML, CSS, and JavaScript. Enable server-side compression (gzip or brotli). Use lazy loading for images (loading="lazy"). Split large JavaScript bundles using code splitting. Remove unused CSS with PurgeCSS or similar tools. Use a CDN to serve pre-compressed assets from edge locations.
Learn more from an authoritative source:
MDN Web DocsJSON Formatter & Validator
Format, validate, and minify JSON — with clear error messages for invalid input.
Base64 Encoder / Decoder
Encode plain text to Base64 or decode Base64 strings back to readable text.
URL Encoder / Decoder
Encode special characters in URLs (percent-encoding) or decode percent-encoded URLs.
UUID Generator
Generate UUID v4 (random) identifiers — one or in bulk.
Results are estimates for informational purposes only and do not constitute professional financial, medical, legal, or technical advice. Read full disclaimer →