📏 Page Size Checker
By Shihab Mia · Updated 2026-06-27
Enter any public web address and select Check page size. We fetch the page once and report its download size in KB and MB, the HTTP status, content type, server and load time. Nothing is fetched until you click.
This page size checker measures how many bytes a web page actually downloads, then shows that size in KB and MB along with the HTTP status, content type, server and load time. Paste any public URL, click the button, and get a clear read on whether a page is lean, average or heavy. It runs free in your browser with no signup.
What is the Page Size Checker?
Page size is the number of bytes a browser has to download to render something. A page size checker turns that abstract number into something you can act on: a clear measurement in kilobytes and megabytes for any URL. Every byte costs time, and on slow mobile connections those bytes add up to seconds of waiting, higher bounce rates and lost rankings. Knowing the size is the first step to making a page faster.
There are two layers to page weight, and it helps to be precise about which one this page size checker reports. The first layer is the HTML document itself, the raw markup the server sends back when you request the URL. The second layer is the total page weight: that HTML plus every image, font, script, stylesheet and tracking pixel the page then pulls in. This tool measures the first layer accurately, the actual bytes of the response at the URL you give it. That single document size is a strong, honest signal, because a bloated HTML document (often caused by inlined data, huge DOMs or unminified output) is a problem you can fix directly.
Why does HTML document size matter on its own? Because it is the very first thing that travels across the network, and the browser cannot start rendering or discover other resources until it arrives. A 30 KB HTML response begins painting far sooner than a 600 KB one. Search engines also crawl billions of pages, and lighter documents are cheaper and faster to fetch, which is part of why page speed is a confirmed ranking factor. A page size checker gives you the raw number that other speed tools build their scores on top of.
The HTTP status code reported alongside the size tells you whether you measured what you meant to. A 200 means the page returned normally. A 301 or 302 means you were redirected, so the size and final URL belong to a different address than the one you typed. A 404 or 410 means the page is missing, and any bytes returned are an error page, not real content. A 500 or 503 means the server itself failed. Reading status and size together stops you from optimising a page that is actually broken.
Content type and server round out the picture. The content type confirms the response really is HTML (text/html) rather than JSON, a PDF or an image, which matters when a URL can return different formats. The server header hints at the technology stack behind the site, useful context when you are comparing your own pages against competitors. None of this requires you to install anything: the page size checker does the fetch on the server and hands you a clean report.
Used regularly, a page size checker becomes a simple discipline. Check a page before and after a redesign. Check a template after a developer adds a new widget. Check a competitor to see how lean a top-ranking page can be. The number is small and concrete, and small concrete numbers are exactly what you need to keep a site fast over the long run.
When to use it
- Auditing a page before and after a redesign to confirm the new HTML is not heavier than the old one.
- Spotting bloated templates after a developer adds a new widget, banner or third-party embed.
- Comparing your page weight against a top-ranking competitor to see how lean fast pages can be.
- Checking that a published page returns HTTP 200 and the right content type, not a stray redirect or error.
- Quickly diagnosing why a page feels slow by confirming whether the HTML document itself is oversized.
- Documenting page size as part of an SEO or performance report for a client or stakeholder.
How to use the Page Size Checker
- Paste the full address of the page you want to test into the URL field. The page size checker pre-fills https://example.com so you can try it instantly.
- Click "Check page size". Nothing is fetched until you click, which keeps the tool fast and respectful of resources.
- Wait for the loading indicator while our server fetches the page once and weighs the response. This usually takes a few seconds.
- Read the result cards: download size in KB and MB, load time in milliseconds, and the HTTP status code returned by the server.
- Scroll the details table to see the final URL after redirects, the exact content type, the reported server software and the raw byte count.
- Use "Copy summary" to grab a one-line report, or "Open page" to view the live URL in a new tab. Test another address any time.
Formula & method
Worked examples
You test a clean marketing landing page and the checker returns 184,320 bytes with HTTP 200.
- Read the raw byte count: 184,320 bytes.
- Convert to KB: 184,320 / 1024 = 180.00 KB.
- Convert to MB: 184,320 / 1,048,576 = 0.176 MB.
- Check the status: HTTP 200 means the page returned normally, so the size is real content.
Result: A 180 KB HTML document is lean and loads fast. No action needed on document weight.
You check a content-heavy article URL and get 3,355,443 bytes with HTTP 200, content type text/html.
- Read the bytes: 3,355,443 bytes.
- Convert to KB: 3,355,443 / 1024 = 3,276.80 KB.
- Convert to MB: 3,355,443 / 1,048,576 = 3.200 MB.
- Flag it: a 3.2 MB HTML document is heavy. Likely causes are inlined base64 images or a very large DOM.
Result: The page size checker marks this as a heavy page. Move inlined images to real image files and minify the HTML to cut the weight.
You enter an old URL and the checker shows a final URL different from what you typed, with HTTP 301 noted before the 200.
- Notice the "Redirected" badge and compare the Final URL row to your input.
- The 301 means the original address permanently moved.
- The reported size belongs to the destination page, not the old URL.
- Re-run the checker on the final URL directly for a clean, single-hop measurement.
Result: You confirmed a redirect chain and now measure the real destination, avoiding a misleading size reading.
Rough HTML document size bands used by this page size checker
| Document size | Band | What it usually means |
|---|---|---|
| Under 100 KB | Very lean | Minimal, fast first byte to paint. Typical of well-built pages. |
| 100 KB to 1 MB | Lean to average | Normal range for most content pages with reasonable markup. |
| 1 MB to 3 MB | Average to heavy | Watch for inlined images, large DOMs or unminified output. |
| Over 3 MB | Heavy | The HTML alone is too large. Investigate and trim before shipping. |
HTTP status codes you may see beside the page size
| Status | Meaning | Effect on your size reading |
|---|---|---|
| 200 OK | Page returned normally | The measured size is real page content. |
| 301 / 302 | Redirect to another URL | Size belongs to the final destination, not your input. |
| 404 / 410 | Page missing or gone | Any bytes returned are an error page, not content. |
| 500 / 503 | Server error or unavailable | No valid page to measure. Retry later or fix the server. |
Common mistakes to avoid
- Assuming this is the total page weight. This page size checker measures the single HTML document returned by the URL, not every image, script and font the page later loads. For full page weight including all assets, use a waterfall tool. The document size is still the right first number to fix.
- Ignoring a redirect before reading the size. If the result shows a "Redirected" badge and a different final URL, you measured the destination, not the address you typed. Re-run the check on the final URL for a clean single-hop reading.
- Optimising a page that returned an error. A 404 or 500 still returns bytes, but those bytes are an error page. Always confirm HTTP 200 before treating the size as real content to optimise.
- Confusing KB and KiB conventions. Browsers and developer tools use the binary convention: 1 KB equals 1024 bytes and 1 MB equals 1,048,576 bytes. This checker uses the same convention so its numbers line up with your dev tools network tab.
- Testing a logged-in or geo-blocked page. The checker fetches the page as an anonymous visitor from a server. Pages behind a login, paywall or country block may return a different, smaller response than what a signed-in user sees.
- Reading one measurement as gospel. Server-rendered pages can vary in size between requests as content changes. For a fair view, check a page a couple of times and compare, especially on sites with dynamic or personalised content.
Glossary
- Page size
- The number of bytes that must be downloaded to receive a web document. Lower is faster.
- Byte
- The basic unit of digital data. One kilobyte (KB) is 1024 bytes and one megabyte (MB) is 1,048,576 bytes.
- HTML document
- The raw markup a server returns for a URL, before the browser loads any extra images, scripts or styles.
- Total page weight
- The combined size of the HTML plus every asset (images, fonts, scripts, styles) a page loads. Larger than the document alone.
- HTTP status code
- A three digit code the server returns to describe the result, such as 200 OK, 301 redirect or 404 not found.
- Content type
- A response header (such as text/html) that states what kind of file the URL returned.
- Redirect
- A server instruction (status 301 or 302) that sends the request to a different URL than the one you asked for.
- Load time
- The time, here in milliseconds, taken to send the request and finish downloading the response from the target server.
Frequently asked questions
What does this page size checker measure?
It measures the exact byte size of the HTML document returned by the URL you enter, then shows that size in KB and MB. It also reports the HTTP status, content type, server and the load time in milliseconds. It is the real downloaded size, not an estimate.
How do I check the size of a web page?
Paste the page address into the field, then click "Check page size". This web page size checker fetches the page once on our server, weighs the response, and shows you the size in kilobytes and megabytes along with the HTTP status and load time.
Does the page size checker include images and scripts?
No. It measures the single HTML document the URL returns, not the combined weight of every image, script, font and stylesheet the page then loads. The document size is the right first number to optimise. For full asset weight, use a waterfall or page speed tool alongside this one.
What is a good web page size?
For the HTML document alone, under 100 KB is very lean and under 1 MB is comfortable for most pages. Above 1 MB the document is getting heavy and worth investigating, and above 3 MB the HTML itself is too large and should be trimmed.
Why does the size shown differ from my browser dev tools?
This checker reports the uncompressed body it downloads. Your browser may show a compressed transfer size (gzip or brotli) and a separate larger resource size. Both are valid views. The page size checker uses the binary convention (1 KB = 1024 bytes) so the numbers align closely with the resource size in your dev tools.
Why did I get a redirect or a non-200 status?
A 301 or 302 means the URL moved, so the size belongs to the final destination shown in the results, not your input. A 404 means the page is missing and any bytes returned are an error page. A 500 or 503 means the server failed. Always confirm a 200 status before treating the size as real content.
Can it check a page behind a login or paywall?
No. The page size checker fetches the URL as an anonymous visitor from a server, so it cannot pass logins, cookies or paywalls. Pages that require sign in may return a different, usually smaller, response than what a logged-in user sees.
Is this page size checker free, and where does the data come from?
Yes, it is completely free with no signup. The data comes from a single live HTTP request our own server makes to the URL you enter; we read the response size and headers and show them to you. We do not store the pages you check or sell any data, and we only fetch when you click the button.
Why measure HTML page size for SEO?
The HTML document is the first thing a browser downloads, and rendering cannot start until it arrives. Lighter documents paint sooner, are cheaper for search engines to crawl, and feed directly into page speed, which is a confirmed ranking factor. Tracking document size is a fast, concrete way to keep pages quick.
How can I reduce my page size after checking it?
Minify your HTML, remove inlined base64 images and load them as real image files, trim unused inline scripts and styles, cut down very large DOMs, and enable gzip or brotli compression on the server. Re-run this page size checker after each change to confirm the document got lighter.