fundamentals
Page weight vs. page speed: what matters for SEO
Page weight and page speed sound interchangeable, but Google treats them differently. Here's what each one is, how they're measured, and what to optimize first.
If you've ever sat in a meeting where someone said "the page is too heavy" and meant "the page is too slow," you know the problem. The two terms get conflated constantly. Google treats them as separate signals, and the fixes for each are different.
The short version
Page weight is how many bytes the page is: HTML plus CSS plus JS plus images plus fonts, all of it. Page speed is how quickly the page becomes usable for the visitor. You can have a fast 4MB page (great CDN, optimized critical path, lazy loading) and a slow 200KB page (one blocking third-party script, awful TTFB). They measure different things.
How Google uses each
Page weight isn't a ranking signal. The 2MB rendered-HTML cap is about indexing, not ranking: anything past 2MB doesn't get read by Googlebot, but below that cap, page weight doesn't directly affect where you rank. The other documented limits (64MB for PDFs, 15MB as a broader crawler cap) are about fetcher behavior, not ranking either.
Page speed is a ranking signal, expressed through :
- LCP (Largest Contentful Paint): when the largest visible element finishes rendering. Target: under 2.5s.
- INP (Interaction to Next Paint): how responsive the page feels when you interact. Target: under 200ms. Replaced FID in March 2024.
- CLS (Cumulative Layout Shift): how much content jumps around as the page loads. Target: under 0.1.
Those three metrics directly affect search rankings, mobile usability rankings, and how Google decides to surface a page.
Where they overlap (and where they don't)
The pattern: page weight is binary at the 2MB threshold (you're either fully indexed or you're not). Page speed is a continuous spectrum that affects ranking gradually.
What to fix first
If your rendered HTML is over 2MB, that's the hard problem. Content past the cutoff isn't reaching Google. Fix this before anything else; see .
If your rendered HTML is under 2MB but your LCP is bad, the problem is page speed. Common fixes include preloading the LCP image with <link rel="preload" as="image">, self-hosting fonts and using font-display: swap, deferring or async-loading non-critical scripts, moving below-the-fold images to loading="lazy", and improving TTFB (CDN, edge caching, faster server).
If both are bad, fix page weight first. Bringing a 3MB page down to 800KB usually fixes LCP as a side effect, since there's just less to download and parse.
A useful mental split
Page weight is a question of whether Google can see all your content. Page speed is a question of how quickly users see it. Both matter, and they're independent levers.
For SEO specifically: the 2MB rendered-HTML cap is the only page-weight number that matters. Anything below it is fine from an indexing standpoint. Anything above it is invisible to Google. to find out which side of the line you're on.
Check your page size now
Test any URL against Google's 2MB Googlebot HTML limit in seconds.
Run a check
