Page Size Checker
Check how heavy a page is in bytes and KB so you can spot bloated URLs, oversized markup, and pages that likely need performance cleanup.
Enter a URL
Use this as a quick size snapshot, then dig deeper if a page looks unusually heavy compared to the rest of your site.
Consider this your site's personal fitness trainer — without the annoying pep talks. Page weight is one of the simplest performance metrics and one of the most neglected. If your site takes longer to load than a three-toed sloth running a marathon, you're going to lose visitors faster than you can make excuses. This tool breaks down the total size of any URL into its component parts so you can see exactly what's weighing your pages down. Time to put your site on a diet.
Key takeaways
- Lighter pages rank better and convert higher. Google uses Core Web Vitals as a ranking signal, and page size directly affects load time. Users on slower connections abandon heavy pages before they finish loading.
- Images are almost always the biggest culprit. On most pages, images account for 50 to 70 percent of total weight. Compressing them and serving modern formats is the highest-impact optimization.
- JavaScript bloat is the second biggest offender. Third-party scripts, analytics, chat widgets, and unminified bundles add up fast. Each script also blocks rendering until it loads.
- Under 1 MB is a solid target for most pages. Content-heavy pages may exceed this, but the tighter you keep total weight, the faster the experience for everyone, especially on mobile.
Ideal Page Sizes
There is no single magic number, but here are practical benchmarks based on what performs well in both search and user experience. A landing page or homepage should aim for under 1.5 MB total. Blog posts and article pages should stay under 1 MB if possible. Tool pages and simple utilities should be under 500 KB since they are functional, not visual.
The median webpage in 2026 weighs roughly 2.5 MB. That means half the web is heavier. Being lighter than the median puts you ahead of most competitors on speed alone. If your page is under 1 MB, you are in the top tier for load performance. Remember: it's the difference between a site that soars and a site that snores. Don't be the snooze-fest.
Mobile matters more than desktop here. A 2 MB page loads in under a second on a fast office connection but can take five seconds or more on a mid-range phone over a 3G network. If your traffic skews mobile (and for most sites it does), page weight should be a top priority.
How to Reduce Page Weight
Compress and resize images. Use WebP or AVIF instead of PNG and JPEG where browser support allows. Serve images at the actual display size rather than uploading a 4000-pixel-wide photo and letting CSS scale it down. Lazy-load images below the fold so they only download when the user scrolls to them.
Minify and bundle JavaScript. Remove unused code, combine small files, and defer scripts that are not needed for the initial render. Every third-party script you add (analytics, chat, social embeds) increases page weight and blocks rendering. Audit them ruthlessly.
Optimize CSS delivery. Inline critical CSS for above-the-fold content and load the rest asynchronously. Remove unused CSS rules. A CSS file for a full framework that the page only uses 20 percent of is dead weight.
Enable compression and caching. Gzip or Brotli compression at the server level can reduce transfer sizes by 60 to 80 percent. Proper cache headers mean returning visitors do not re-download assets they already have.
FAQ
What is considered a "heavy" page?
Does page size directly affect SEO rankings?
What is the difference between page size and transfer size?
Related Tools
Popular SEOLivly Tools
About Page Size Checker
It reports bytes. It does not tell you which image is heavy, which script is blocking, or what the page costs on a phone. A 2 MB page can feel fast if the bytes arrive in the right order, and a 300 KB page can feel slow if the server takes two seconds to start.
Use it as the first number, then look at the images and scripts. The usual culprit is a hero image that was uploaded at 4,000 pixels and displayed at 800. The second usual culprit is a page builder loading six libraries for one accordion.
The website auditor lists the scripts and stylesheets. The Fix Sprint handles the cleanup.