Page Size Checker
Fast, accurate results in seconds.
The Page Size Checker checks the total download size of a webpage, including all its assets. Enter a domain or URL and get the results instantly, with no signup required.
This kind of lookup is useful for SEO audits, competitive research, troubleshooting site issues, or simply verifying technical details about a website before you rely on it.
How to Use the Page Size Checker
- Enter the domain or URL you want to check
- Click Check
- Review the results
Best Practices
- Recheck periodically, as DNS, hosting and authority data can change over time
- Cross-reference results with other tools for critical decisions
This tool is free to use with no signup required.
Frequently Asked Questions
What does a page size checker measure?
It measures the total download size of a webpage, including HTML, CSS, JavaScript, images, and other resources loaded to fully render the page.
Why does page size matter for SEO?
Larger page sizes generally mean slower load times, which can hurt both user experience and search rankings, since Google factors page speed into its ranking signals.
What is a good target page size?
There's no universal number, but many performance guidelines suggest keeping total page weight under 1-2 MB where possible, especially for mobile users on slower connections.
Is this tool free to use?
Yes, completely free with no signup, no limits and no software to install.
Is my data saved anywhere?
No — checks run on request and are not stored or linked to you.
What typically makes a page size too large?
Unoptimized images are the most common culprit, followed by excessive JavaScript libraries, unminified CSS/JS, and too many third-party scripts (ads, trackers, widgets).
How can I reduce my page size?
Compress and properly size images, minify CSS/JS, remove unused scripts, enable compression (like gzip or Brotli) on your server, and lazy-load offscreen content.
Does page size directly determine Core Web Vitals scores?
Page size is a major contributing factor to load-related Core Web Vitals metrics (like Largest Contentful Paint), but other factors like server response time and rendering-blocking resources also play a significant role.
Is this useful for comparing my site against competitors?
Yes — checking competitor page sizes can provide a useful benchmark for how lean or heavy your own pages are relative to others in your space.
Does this account for cached resources on repeat visits?
This typically measures the full initial page weight — actual load time for repeat visitors is often faster due to browser caching of previously downloaded resources.
The Page Size Checker measures the total download weight of a webpage — HTML, CSS, JavaScript, images, and other assets combined — revealing exactly how much data a visitor's browser has to download to render it.
Why Total Page Weight Directly Affects Real Users
Every additional kilobyte a page requires means more time spent downloading before a visitor can see and interact with content, an effect that compounds heavily on slower mobile connections. Page weight is also one of the underlying factors behind Core Web Vitals metrics like Largest Contentful Paint, which Google explicitly factors into search rankings, making page size a metric with both a user experience and an SEO dimension.
What Typically Contributes Most to Page Weight
- Images — usually the single largest contributor on most pages, especially uncompressed or oversized photos.
- JavaScript — large bundled scripts, especially from third-party widgets, trackers, and ad networks, can add significant weight beyond a site's own code.
- Web fonts — custom fonts, particularly multiple weights and styles loaded unnecessarily, add up faster than most site owners expect.
- CSS — typically a smaller contributor than images or scripts, but unused or bloated stylesheets still add unnecessary weight.
Common Use Cases
Diagnosing why a page loads slowly despite looking simple, benchmarking page weight against competitors, and verifying that image compression or code optimization efforts actually reduced total page size after implementation.
