You've probably checked your page speed before. But have you ever looked at your page size — the total weight of everything your page downloads? It matters more than most people think.
Page size is the total amount of data a browser needs to load to render your page: HTML, CSS, JavaScript, images, fonts, videos, and third-party scripts all count. The heavier the page, the longer it takes to download — especially on mobile networks — and the more Google has to think about whether your page is worth the crawl budget it spends on it.
So what is a good page size for SEO? Let's dig into the numbers, why they matter, and how to slim your pages down.
Google has been clear that page experience affects rankings. Core Web Vitals — Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift — all get worse on heavy pages. A bloated page doesn't just load slowly; it stutters, shifts layout as elements load, and frustrates visitors on phones. It also eats crawl budget (heavy pages cost Google more bandwidth per crawl, so fewer of your pages may get indexed) and drives up bounce rates — a page that takes five seconds on 4G loses visitors before they see your content.
The good news: page size is one of the easiest technical SEO factors to measure and fix. Before optimizing anything, check your current page size to see where you stand.
There is no single official number from Google, but industry data paints a clear picture:
For context, the median page on the web is now well over 2 MB. Hitting under 1 MB genuinely puts you ahead of the pack. These are guidelines, not laws — a photo portfolio will naturally weigh more than a blog post. The key question: does every kilobyte earn its place? If not, cut it.
Before fixing anything, it helps to know what typically bloats a page. In most audits I do, the same culprits show up:
Images are the number one source of page bloat. A single uncompressed hero image can outweigh everything else on the page. Classic issues: 5 MB JPEGs uploaded straight from the camera, PNGs used where JPEGs would do, and oversized images served to devices that can't display them.
Analytics, chat widgets, heatmaps, ad scripts, social embeds — each adds weight and competes for the browser's main thread. Render-blocking JavaScript is especially damaging because it delays the moment your content becomes visible.
Custom fonts are beautiful but heavy. Each weight and style is a separate file. Some sites load five or six font files — that's easily 300–500 KB before anything else renders.
A full-width autoplaying video can add 5–20 MB to a page. It looks stunning on fast office Wi-Fi and terrible on a phone in a parking garage. If you must use video, compress it aggressively and consider serving it only to desktop users.
Google Maps, social media feeds, booking widgets, review badges — every embed pulls in its own scripts, styles, and images. Each one is a performance tax you don't control.
Once you know your number, here's how to bring it down. Start with the biggest wins.
Convert images to WebP or AVIF (25–35% smaller than JPEG at equal quality), serve responsive images (srcset) so phones download smaller versions, and never serve an image larger than the space it displays in.
Lazy loading defers images and iframes until they're about to scroll into view. Your initial page load only includes what's visible — everything else loads later. Most modern browsers support this natively with the loading="lazy" attribute.
Remove whitespace, comments, and unused code from your CSS and JS (minification). Then defer non-critical scripts so they load after the page renders. Audit your plugins and scripts regularly — if you're not actively using that heatmap tool, remove it.
Stick to one or two font families and only the weights you use. Add font-display: swap so text renders instantly with a fallback while your custom font loads.
Ask whether every widget earns its weight. Replace a live social feed with a static link. Swap the Google Maps embed for a screenshot that links to the map. Self-host what you can.
Make sure your server uses Brotli or GZIP compression — this alone can cut text-based assets (HTML, CSS, JS) by 60–80%. Set proper cache headers so returning visitors don't re-download everything.
After making changes, re-run the page size checker to confirm the improvement. Pair it with a page speed test or a PageSpeed Insights check to see how the lighter page performs in Google's own scoring — the two metrics should improve together.
Page size isn't a Core Web Vital itself, but it's the lever that moves them. A lighter page almost always means faster Largest Contentful Paint (the hero element downloads sooner), better Interaction to Next Paint (less JavaScript competing for the main thread), and lower Cumulative Layout Shift (fixing image dimensions and font loading as part of slimming down eliminates layout shifts). Optimize the input and the output follows.
Anything over 2 MB is generally considered large for a content page, and over 3 MB is excessive. The sweet spot for SEO is under 1 MB, with 1–2 MB being acceptable for most sites.
Page size itself isn't a direct ranking factor, but it strongly influences page experience signals that are: loading speed, Core Web Vitals, and bounce rate. Heavy pages rank worse in practice because they score poorly on all three.
Page size is how much data a page contains (measured in KB/MB). Page speed is how long it takes to load (measured in seconds). They're closely related — smaller pages usually load faster — but server response time and script execution also affect speed independently of size.
Use an online tool that fetches your page and reports the total transfer size plus a breakdown by resource type. Seovaro's free page size checker does exactly this — just enter your URL and you'll get your page weight in seconds.
Yes, especially. Mobile users are more likely to be on slow or metered connections, and Google predominantly uses the mobile version of your page for indexing and ranking. A page that's fine on desktop can be painfully slow on a phone.
A good page size for SEO is under 1 MB, with anything under 2 MB being perfectly respectable. Most of the web is heavier than it should be, which means slimming down is an easy way to get ahead.
Measure first, fix the big offenders (images, scripts, fonts), and re-measure. It's one of the few SEO tasks where the before-and-after is visible in an afternoon.
Ready to find out where your pages stand? Run a free check with Seovaro's Page Size Checker — enter your URL and get your page weight plus a breakdown of what's making it heavy, in seconds.
