Web Page Size Checker
Measure the total download weight of any page and see exactly which files are slowing it down. Enter a URL to get a full breakdown in seconds.
Total page weight
Every byte the browser downloads to render your page, measured as it travels over the wire.
Breakdown by file type
HTML, CSS, JavaScript, images and fonts, each with its own size and request count.
A shareable report
Save the result as a PDF or copy a link that reruns the same check for your developer or client.
Auditing your page
Breakdown by resource type
Transferred size—
What is the Web Page Size Checker?
Page size, also called page weight, is the total number of bytes a browser downloads before your page finishes rendering. That includes the HTML document plus every stylesheet, script, image, web font and third-party tag the page pulls in. A page that reads as light and simple can still weigh 4 MB once an uncompressed hero image, three font weights and a chat widget are counted.
RankUp4u’s Web Page Size Checker loads your URL in a real headless Chrome browser, records every network request the way a visitor’s browser would, and reports the transferred size grouped by resource type. You get the total weight, a request count, a verdict grade and a breakdown that shows which category is responsible for the bulk of the download, without installing anything or opening developer tools.
How the tool can assist you
Find the files that are actually slowing the page down
Instead of guessing, you see which resource type dominates the download and how many requests each one costs. In most audits a handful of oversized images or one unused JavaScript bundle accounts for the majority of the weight.
Set a realistic weight budget for new templates
Check a page before and after a design change and you have a number to hold the template to. Performance budgets only work when someone can measure them in seconds, which is what this tool is for.
Benchmark against competitors
Run the same test on a competitor’s equivalent page. If their product page loads at 900 KB and yours is at 3.4 MB, that gap shows up in Core Web Vitals field data and in bounce rate on mobile.
Hand developers something specific
Save the report as a PDF or share the result link. A breakdown with sizes attached is far easier to action than a request to “make the site faster”.
Key features of the tool
Real browser measurement
Requests are recorded from a full Chrome render, so lazy-loaded and script-injected assets are counted, not just what appears in the HTML source.
Transferred vs. uncompressed size
Sizes reflect what actually travels over the wire after Gzip or Brotli, which is the number that determines load time for your visitors.
Breakdown by resource type
Images, JavaScript, CSS, fonts, HTML and other files, each with request count, size and share of the total page weight.
Verdict grade and benchmark
A letter grade plus a comparison against the current web median, so you know whether the number you are looking at is a problem.
Shareable PDF report
Export the full result or copy a link to send to a client, a developer or your own records for a before-and-after comparison.
Free and unlimited
No signup, no credit card and no cap on the number of URLs you can test. Works on any public page, including staging sites that are not password protected.
How to use the Web Page Size Checker
The whole test takes under a minute. There is nothing to install and no account to create.
Paste the full URL of the page you want to test
Use the exact address a visitor would land on, including any path or query string. Test the page that matters commercially, not just the homepage. Product, category and blog templates usually carry more weight.
Click Start Audit and wait for the render
The tool resolves redirects, opens the page in Chrome, waits for the network to settle and records every request. Most pages finish in ten to thirty seconds; very heavy pages take longer because we wait for lazy-loaded assets.
Read the breakdown and act on the largest category
Start with whichever resource type owns the biggest share. Fixing the top category almost always delivers more than a dozen small optimisations elsewhere. Then re-run the test to confirm the saving.
Export or share the report
Save the PDF for your audit documentation, or copy the result link so a developer can open the same check you did.
How to read your results
- Total page size
- The sum of all transferred bytes. This is the headline number and the one to track over time.
- Requests
- How many separate files the browser had to fetch. High request counts hurt even when the total size is small, because each connection carries overhead.
- Verdict grade
- A to F, based on total weight and request count relative to current web norms. A is under 1 MB, B up to roughly 2.5 MB, and anything at D or below needs work before it affects rankings.
- Resource breakdown
- Size and share per file type. Images above 50% points to a compression problem; JavaScript above 30% usually means unused bundles or too many third-party scripts.
- Comparison to average
- Your page against the 2.2 MB web median. Useful context, but your real target is your own competitors, not the average of the whole web.
What is a good web page size?
There is no single correct number, because a photography portfolio will always outweigh a documentation page. These are the ranges we work to when auditing client sites.
How page size affects SEO
Google does not rank pages on file size directly. It ranks on the user experience that file size produces, which means page weight reaches your rankings through several separate paths.
How to reduce your web page size
Work down this list in order. The first three items resolve the majority of page weight problems we see.
1. Compress and resize images
Serve WebP or AVIF instead of JPEG and PNG, generate the sizes your layout actually displays, and use responsive srcset so phones never download a 2000px hero. This alone typically cuts 40 to 60% of page weight.
2. Cut unused JavaScript and CSS
Audit your bundles and remove code paths the page never runs. On WordPress sites, plugins that enqueue their assets site-wide are the usual cause. Defer anything not needed for first paint.
3. Enable Brotli or Gzip compression
Text assets should never travel uncompressed. Brotli typically beats Gzip by 15 to 20% on HTML, CSS and JavaScript, and it is a server setting rather than a code change.
4. Lazy-load below-the-fold media
Add loading="lazy" to images and iframes outside the viewport, and replace autoplaying video with a poster image plus click-to-play.
5. Subset and self-host fonts
Ship only the weights and character ranges you use, in WOFF2, from your own domain. Four weights of two families can quietly cost 300 KB and an extra DNS lookup.
6. Audit third-party scripts
Tag managers, chat widgets, heatmaps, A/B testing and ad scripts add weight you do not control. Remove anything nobody has looked at in six months, and load the rest after interaction where possible.
Frequently asked questions
What is a good web page size?
Under 1.5 MB is a safe target for most content pages. Ecommerce and media-heavy pages often land between 2 and 3 MB, which is workable if images are lazy-loaded and compressed.
Does page size affect Google rankings?
Indirectly. Google ranks on Core Web Vitals, and page weight is the single biggest driver of Largest Contentful Paint and slow load times on mobile.
What counts toward page size?
Everything the browser downloads: the HTML document, stylesheets, scripts, images, video posters, web fonts, and any third-party tags such as analytics or chat widgets.
How do I reduce my page size?
Compress and resize images, serve WebP or AVIF, enable Brotli compression, remove unused CSS and JavaScript, self-host only the font weights you use, and audit third-party scripts.
Is this tool free?
Yes. There is no limit on the number of pages you can check and no signup is required.
What is the difference between page size and load time?
Page size is how many bytes get downloaded; load time is how long that takes on a given connection. Size is the cause you control, load time is the outcome your visitors experience. Two pages of the same weight can load at very different speeds depending on server response, compression and request order.
Why does your result differ from another page size tool?
Tools differ in what they count. Some measure only the HTML source, some report uncompressed sizes, and some stop before lazy-loaded assets fire. We measure transferred size from a full Chrome render after the network settles, which is closest to what a real visitor downloads.
Can I check a page behind a login or on staging?
Any publicly reachable URL works, including staging domains that are not password protected. Pages behind authentication, a paywall or an IP allowlist cannot be loaded by the tool.
Does the tool test mobile or desktop?
Results shown here are from a desktop viewport. Because most sites serve the same assets to both, the totals are usually close, though responsive images mean a mobile render can be lighter.
How often should I check page size?
Any time a template changes, a plugin is added or a new campaign page goes live. On active sites a monthly check of your top ten landing pages catches regressions before they show up in Search Console.
Other free SEO tools from RankUp4u
Page weight is one input. These cover the rest of the technical checklist.
Page too heavy to fix on your own?
Our technical SEO team audits page weight, Core Web Vitals and crawl health, then ships the fixes. Get a free audit of your site.
