
Key takeaways
- Backlinko and Ahrefs analyzed 11.8 million Google search results and found no correlation between page HTML size and ranking position.
- The same dataset showed zero correlation between page loading speed and first page rankings, with an average load time of 1.65 seconds.
- The study measured page HTML size and load speed only, not the number of HTTP requests or a mobile versus desktop split.
- Backlinko's own authors describe the results as correlational, stating it is impossible to determine the underlying reason behind any pattern.
- No correlation to rankings is not proof that page weight is irrelevant, since a bloated page can still hurt conversions and crawl efficiency on its own terms.
The idea that a bloated page drags down its own rankings is one of the oldest pieces of technical SEO folklore. It has an intuitive story behind it: heavier pages load slower, slower pages frustrate users, and Google is said to reward what users like. The largest publicly available correlation study to test that story directly found nothing.
What the study measured
Backlinko, working with Ahrefs as a data partner, pulled ranking and on-page data for 11.8 million Google search results and ran correlation analysis across a long list of on-page and off-page factors. Two of those factors sit directly on the question this piece is asking: page HTML size, and page loading speed. The published article states the result for size under the heading “Page HTML Size Has No Relationship With Rankings,” and reports “we found no correlation between page size and rankings.” For loading speed, the finding is the same in kind: “Overall, we found zero correlation between site speed and Google rankings,” with first-page results averaging 1.65 seconds to load.
What it does not measure
Two gaps matter for anyone tempted to read this as settling the mobile page-weight question. The study reports HTML byte size, not the full transferred weight of a page once images, scripts, fonts, and third-party tags are counted, so it is a narrower measurement than “total page weight.” It also does not report a count of HTTP requests per page anywhere in the public write-up, so there is no sourced basis here for a claim about request count and rankings, even though request count is a common companion metric to byte size in page-speed audits. Anyone citing this study for either of those two specific claims would be extending it past what it actually measured.
Why a null correlation is still worth reporting
A finding of “no correlation” is not the same as “no effect never happens,” and the study’s own authors are explicit about that limit: “As this is a correlation study, it’s impossible to determine the underlying reason” behind any pattern in the data. An aggregate correlation across 11.8 million results, spanning every niche and query type Ahrefs’ index covers, can wash out an effect that is real but confined to a narrower slice, such as e-commerce category pages competing on load speed against each other specifically. The honest reading is that at this scale, page size and page speed are not acting as a broad, direct ranking lever, not that no page has ever been held back by its own weight.
What this means for prioritizing the work
Do not sell a page-weight reduction project on the promise of a ranking jump; the largest public correlation study on the question found none. Do sell it on what it actually protects: Core Web Vitals pass rates, conversion rate, crawl efficiency on large sites, and the experience of users on constrained mobile connections, none of which need a ranking correlation to be worth fixing on their own.
The evidence
- Sample
- 11.8M search results (Backlinko x Ahrefs)
Hypothesis: Pages with a smaller total HTML byte size rank measurably higher in Google search results than heavier pages, on the theory that "bloated" markup disadvantages a page in ranking.
Method: Backlinko, working with data partner Ahrefs, pulled ranking and page data for 11.8 million Google search results and measured the correlation between page HTML size and first-page ranking position, alongside a separate measurement of page loading speed against ranking position. The published write-up does not state which correlation coefficient was used, nor does it break the page-size or speed measurements out by device, so a mobile-specific reading of the result cannot be verified from the public article. The study measures HTML byte size and load time only; it does not report a count of HTTP requests per page, so no claim about request count and rankings can be sourced to this study. As a correlation study, it cannot establish that page weight causes any ranking outcome, only whether the two move together across the sample.
Findings
- Backlinko and Ahrefs found no correlation between page HTML size and Google rankings across 11.8 million search results, publishing this under the heading 'Page HTML Size Has No Relationship With Rankings.'
- The same study reports zero correlation between page loading speed and first-page rankings, with an average load time of 1.65 seconds among first-page results.
- The authors state plainly that because it is a correlation study, 'it's impossible to determine the underlying reason' behind any pattern in the data, which they apply to their findings across the whole analysis.
Limitations: The publicly readable article does not disclose the correlation method (Spearman, Pearson, or otherwise), the date range of the crawl, or the countries and devices the 11.8 million results were drawn from; a separate methodology document is referenced but not reproduced here because it could not be verified against the primary source. The study reports HTML byte size, not total page weight including images, scripts, and fonts, and it does not measure number of requests at all, so this write-up cannot extend the "no correlation" finding to either of those two more specific claims. A null correlation result across a broad, ranking-agnostic sample can also mask a real effect that exists only in specific niches or at specific size extremes, which an aggregate correlation coefficient would not surface.
Sources
- 1.We Analyzed 11.8 Million Google Search Results. Here's What We Learned About SEO - Backlinko, April 14, 2025Primary
About the author

Founder, UpgradIQ FZC LLC
Adam Hafez works on technical SEO and search measurement: how pages get crawled, indexed, ranked and now quoted by answer engines. He founded UpgradIQ, which reads Google Search Console and GA4 to tie ranking movement back to the changes that caused it. He publishes what the data supports and states the limits of it.
- Technical SEO
- Search Console and GA4 measurement
- Answer engine optimization
- Structured data
The briefing
Only what actually changed in search, delivered in full by RSS, Atom or JSON feed.
FollowRelated reading
Nuvemshop lifted good LCP from 57% to 96% by fixing image loading
Nuvemshop's web.dev case study: removing lazy loading on top images and adding fetchpriority took good LCP from 57% to 96% across its stores.
Core Web Vitals by CMS, 2025: Duda and Wix lead, WordPress lags
The 2025 Web Almanac's CMS chapter breaks Core Web Vitals pass rates down by platform: Duda at 85%, Wix up 14 points to 74%, WordPress flat at 45%.
CoinStats fixed a Core Web Vitals bug, tripled search impressions
DebugBear's case study: CoinStats found Base64 images were bloating 15,000 pages, fixed it, and saw Good URLs and search impressions both increase 3x.
Core Web Vitals checker for LCP, INP and CLS scores
Core Web Vitals checker: rate LCP, INP and CLS values as Good, Needs improvement or Poor and see if all three pass. Free, runs in your browser.



