RevealTheme logo

Page Size Analyzer

Fetch any public page's HTML and see its byte size plus a count of the stylesheets, scripts, images, and iframes referenced in the markup.

How to use this tool

  1. 1

    Paste the full URL of a public page (starting with https://) into the input field.

  2. 2

    Click Analyze to have the server fetch that page's HTML.

  3. 3

    Read the result cards: HTML shows the document size in bytes, and the other cards show how many stylesheet links, external scripts, images, and iframes appear in the markup.

  4. 4

    Try a competitor or a previous version of your own page and compare the numbers.

What does the Page Size Analyzer actually measure?

Page weight is the total bytes a browser must download to render a page, and it directly shapes load time, especially on mobile and slow connections. This tool gives you a fast first look at one slice of that weight. It fetches only the page's HTML document and reports its size in bytes (the HTML card), then parses the markup with an HTML parser to count four kinds of referenced resources: <link rel="stylesheet"> tags, <script> tags that have a src attribute, <img> tags, and <iframe> tags. It is important to understand what those numbers are and are not. The byte size is the HTML only; the analyzer does not download the CSS, JavaScript, image, or font files those tags point to, so it cannot tell you their combined transfer size. The counts come from the raw HTML as delivered by the server, so resources injected later by JavaScript, lazy-loaded images, and inline (src-less) scripts are not counted. Pages larger than 5MB are rejected, and fetches time out after 20 seconds. Treat the result as a quick structural snapshot, not a full performance audit.

Common use cases

  • Quickly checking whether a landing page's HTML has bloated to an unusually large byte size before a launch.

  • Counting how many separate stylesheet and external script tags a page loads, to spot bundling or third-party-tag sprawl.

  • Comparing the resource counts of your page against a competitor's to see who ships a leaner front end.

  • Auditing how many img tags a content or product page renders when investigating layout shift or lazy-loading issues.

  • Spotting unexpected iframes (embeds, ad slots, trackers) injected into a page's markup.

  • Sanity-checking a CMS or build change by diffing the HTML size and tag counts before and after a deploy.

Frequently asked questions

Does this measure the full page weight including CSS, JS, and images?▼
No. It measures the size of the HTML document only and counts the resource tags inside it. It does not download the linked CSS, JavaScript, image, or font files, so it cannot report their combined transfer size. For a full byte-by-byte waterfall, use Chrome DevTools or Lighthouse.
Why is the script or image count lower than I expect?▼
The counts come from the raw HTML the server returns. Scripts without a src attribute (inline scripts) are not counted, and any resources or images added later by JavaScript, frameworks, or lazy-loading do not appear in the initial markup, so they are excluded.
Is my data uploaded anywhere?▼
The URL you enter is sent to this site's server, which fetches the target page on your behalf and returns the counts. The analysis runs server-side, not in your browser, so the URL leaves your machine. The page contents are not stored after the response is generated.
Can I analyze a page behind a login or on my local network?▼
No. The fetcher only retrieves publicly reachable pages over a normal request with no cookies, so anything requiring authentication will not work. Private, loopback, and internal addresses are blocked for security, so localhost and intranet URLs are rejected.
What does the HTML number actually represent?▼
It is the byte length of the fetched HTML document as delivered. Responses are decoded as UTF-8, and pages larger than 5MB are rejected with an error rather than measured.
Why did my analysis fail or time out?▼
Common causes are a URL that requires a login, a server that blocks automated requests, a redirect chain longer than five hops, a response over the 5MB limit, or a page that takes more than 20 seconds to respond. Private or invalid hosts are also refused.
What is a reasonable HTML size?▼
There is no fixed rule, but lean content pages often ship well under a few hundred KB of HTML. A very large HTML document can signal inlined data, bloated markup, or server-side rendered content that may be worth trimming.

Related tools

DNS Lookup

Look up DNS records (A, AAAA, MX, TXT, NS) for any domain.

WHOIS Lookup

Get full WHOIS data for any domain.

SSL Certificate Checker

Check SSL certificate validity, issuer, and expiry.

HTTP Header Analyzer

Inspect HTTP response headers and security signals.

HTTP Status Code Checker

Check status code of any URL — single or bulk.

Redirect Chain Tracer

Follow every hop in a redirect chain.

Subscribe for updates

We do not sell your email. We do not spam.

© 2026 RevealTheme. All rights reserved.