Page Size Checker
Enter a URL
About Page Size Checker
Page size — the total data weight of your webpage — is one of the most direct levers you have over loading speed. A page that weighs 3 MB takes measurably longer to deliver than one that weighs 500 KB, on every connection, for every user. Google has confirmed page speed as a ranking signal through Core Web Vitals, and Cloudflare data shows that 53% of mobile visitors abandon pages that take more than 3 seconds to load. The DigitalSub Pro Page Size Checker measures the HTML size and total transfer weight of any URL instantly — so you know exactly how heavy your page is and whether it needs optimisation.
What the Tool Shows
Enter any URL and the tool returns the page's HTML document size (uncompressed) and the compressed transfer size (what actually travels over the wire to the user's browser). Here is a sample result.
Sample result only. In this example: the HTML itself compresses well (189KB → 52KB), but the total page weight of 2.3MB is significantly over the 1MB mobile target, driven by unoptimised images.
Page Size Targets — What's Good, Acceptable, and Too Heavy
There is no single universally "correct" page size — it depends on the type of content your page delivers. A photography portfolio legitimately needs more image data than a text article. But there are clear benchmarks from Google and performance research that tell you whether your page weight is competitive or a problem.
Loads near-instantly on any connection. Top performance scores. Competitive advantage in Core Web Vitals.
Acceptable for most content pages. May need attention on slow mobile connections. Aim for this range.
Above web average. Slow on mobile, increases bounce rate. Optimisation is recommended.
Significantly impacts load time, Core Web Vitals scores, and rankings. Requires immediate attention.
Google recommends keeping the HTML document itself under 100 KB uncompressed. For the total page weight including all resources, the practical target is under 1 MB for mobile and under 1.5 MB for desktop. The web average in 2025 is approximately 2.2 MB — which means most sites are running heavy, and improving page weight is a genuine competitive opportunity.
What Makes a Page Heavy — Resource Breakdown
Understanding which resource types consume the most weight tells you exactly where to focus optimisation effort. The breakdown is consistent across most websites.
| Resource Type | Typical Share of Page Weight | Target | Status |
|---|---|---|---|
| Images | Use WebP/AVIF, lazy-load below fold | Biggest lever | |
| JavaScript | Under 400 KB total, defer unused scripts | Commonly bloated | |
| CSS | Under 100 KB, remove unused styles | Manageable | |
| Fonts | Under 100 KB total, limit to 2 font families | Usually fine | |
| HTML document | Under 100 KB uncompressed (Google's recommendation) | Rarely the problem | |
| Third-party scripts | Audit every tag — each one adds weight and latency | Often hidden weight |
How to Reduce Page Size — Highest-Impact Fixes
Most page weight problems come from a small number of causes. These fixes are ranked by the size reduction they typically deliver — tackle them in order.
Convert Images to WebP or AVIF
Images account for the majority of most pages' weight. Converting from JPEG or PNG to WebP saves 25–34% in file size. AVIF saves 50%+ with equivalent visual quality. Apply to every image across the site — this alone can cut total page weight by 30–50% on image-heavy pages.
Highest ImpactLazy-Load Below-the-Fold Images
Adding loading="lazy" to images not visible on initial load means the browser skips downloading them until the user scrolls. On long content pages this reduces initial page weight by 30–60%. A one-attribute change that delivers immediate load time improvement.
Enable GZIP or Brotli Compression
Server-side compression shrinks HTML, CSS, and JavaScript files by 60–80% during transfer. A 200 KB HTML file compresses to roughly 50 KB. Most hosts support this via a single server configuration line. Brotli (newer) compresses even better than GZIP. There is no valid reason to serve uncompressed HTML in 2025.
High ImpactRemove Unused CSS and JavaScript
Most CMS themes and frameworks load significantly more CSS and JS than any single page needs. Tools like PurgeCSS identify and remove unused CSS rules. Deferring or removing unused third-party scripts (chat widgets, analytics that duplicate, old A/B testing libraries) can remove hundreds of KB from your page weight immediately.
High ImpactLimit Web Fonts
Each font family and weight is a separate HTTP request and file download. Loading four font families with three weights each adds ~400 KB before a single user interaction. Limit fonts to two families maximum, use font-display: swap, and subset fonts to load only the characters your site actually uses.
Audit Third-Party Scripts
Marketing tags, chat widgets, heatmap tools, social sharing buttons — each one adds weight and, more expensively, additional HTTP requests that block rendering. Audit every script in your tag manager. Remove anything inactive. Delay non-critical scripts until after the page has loaded (the defer attribute on script tags).
How to Use the Page Size Checker
Enter Any URL
Paste the full URL of the page you want to check — homepage, landing page, blog post, or product page. Include https://.
Run the Check
Click Submit. The tool fetches the page, measures the HTML document size and compressed transfer size, and returns the result instantly.
Compare to Targets
Check your HTML size against the 100 KB Google recommendation and your total page weight against the 1–1.5 MB target. Use the tips above to reduce any problem areas.
Frequently Asked Questions
Does page size directly affect Google rankings?
Not directly — Google does not rank pages by file size. But page size is one of the primary drivers of page loading speed, and page speed is a confirmed ranking signal through Core Web Vitals (specifically LCP — Largest Contentful Paint, and INP — Interaction to Next Paint). A heavier page takes longer to load, which produces worse Core Web Vitals scores, which in turn negatively affects rankings. The relationship is indirect but well-established: reducing page weight almost always improves speed scores, which improves rankings.
What is the difference between HTML size and total page weight?
HTML size is just the size of the HTML document itself — the text markup, inline scripts, and inline styles that make up the page's raw code. Total page weight includes every resource the browser downloads to fully render the page: the HTML, all linked CSS files, all JavaScript files, all images, fonts, videos, and third-party embeds.
The HTML document is typically a small fraction of the total page weight. A page with a 50 KB HTML document might have a total weight of 3 MB once all its images and scripts are included. This tool measures the HTML document size — for total page weight analysis, pair it with a tool like Google PageSpeed Insights.
What is GZIP compression and why does it matter?
GZIP (and the newer Brotli) is server-side compression that reduces the size of text-based files — HTML, CSS, and JavaScript — before they are transmitted to the user's browser. The browser then decompresses them automatically. A typical HTML document compresses to 20–30% of its original size. This means a 200 KB HTML file transfers as roughly 50 KB over the network — dramatically reducing load time at no cost to the user experience.
Most web hosts and CDNs enable GZIP by default. You can verify your site compresses its HTML by checking the "Transfer Size" result in this tool — if it is significantly smaller than the "HTML Size," compression is working. If both numbers are nearly identical, compression may not be enabled on your server.
My page is 4 MB but still loads fast. Should I still optimise?
Yes — even if your page loads acceptably on your own fast broadband connection, a heavy page is a real problem for users on slower connections: mobile data in emerging markets, 4G with weak signal, or shared networks. 62% of global web traffic is mobile, and connection quality varies enormously. A 4 MB page that loads in 1.5 seconds on fibre may take 8–12 seconds on a 3G connection.
Beyond user experience, Core Web Vitals scores are measured from field data collected from real users across all connection types. If a significant portion of your audience is on slower connections, your field data LCP score will reflect their experience — which is what Google uses in its ranking signals, not the fast load time you experience at your desk.
Is the Page Size Checker completely free?
Yes — completely free, no account, no sign-up, no limits. Check as many pages as you need. This applies to all 47+ tools on DigitalSub Pro.