The Hidden Infrastructure Battle
Google's technical leaders are confronting a fundamental web infrastructure problem that most businesses overlook: the growing divergence between what machines require to understand web content and what users actually experience. The median mobile homepage has tripled from 845 KB in 2015 to 2,362 KB by July 2025, revealing deeper structural issues in how the web is built and consumed.
This development matters because it exposes hidden costs in the pursuit of search visibility. Every additional kilobyte of structured data, JavaScript framework, or high-resolution image represents a strategic trade-off between machine optimization and human experience. For executives, this is not about technical minutiae—it is about understanding how Google's infrastructure decisions create winners and losers in the digital ecosystem.
The Machine-User Tension
Gary Illyes' discussion of structured data reveals the core tension. When Google co-founder Sergey Brin stated early in Google's history that machines should be able to figure out everything from text alone, he established a philosophical foundation now being tested. Structured data exists for machines, not users, yet adding Google's full range of supported structured data types adds invisible weight that visitors never see but still consumes bandwidth and affects performance.
This creates a strategic dilemma for businesses. Implementing comprehensive structured data can improve search visibility and machine understanding. However, every additional schema markup adds weight that degrades user experience, particularly for the 45% of global users who experience slow connections or metered data plans. The tension is economic: businesses must decide whether to prioritize machine readability for search engines or human experience for actual customers.
Google's Infrastructure Control
Google maintains significant control through its crawl infrastructure limits. The 15 MB default across Google's broader crawl infrastructure, with each URL getting its own limit and referenced resources fetched separately, creates a technical boundary that shapes web development. Specifically, Googlebot for Google Search crawls only the first 2 MB of a supported file type and the first 64 MB of a PDF, establishing clear parameters within which businesses must operate.
What is revealing is the flexibility Illyes and Martin Splitt discussed—internal teams can override these defaults depending on what is being crawled. This creates a hidden hierarchy in how Google treats different content. A major news publisher might receive different crawl treatment than a small business website, creating structural advantages for established players who understand how to navigate these technical boundaries.
The Performance Gap
Splitt's observation that page size growth may have outpaced improvements in median mobile connection speeds represents a critical market failure. If true, this means the web is becoming less accessible even as infrastructure improves—a perverse outcome that benefits high-speed internet providers while penalizing users in emerging markets or rural areas.
The data shows this is not hypothetical. When Splitt noted that metered satellite internet made him rethink how much data websites transfer, he identified a real economic impact. For users paying $10.5 billion annually in data overage charges globally, page bloat represents a direct financial cost. For businesses targeting these markets, oversized pages mean lost customers and reduced conversion rates—Illyes referenced studies showing faster websites have better retention and conversion, though specific research was not cited.
Strategic Winners and Losers
The structural implications create clear winners. Google maintains control over the infrastructure while externalizing the optimization burden to website owners. Web optimization service providers see growing demand as page complexity increases. High-speed internet providers benefit as larger page sizes drive demand for faster connections.
The losers are more numerous. Users in areas with slow connections experience degraded performance and higher data costs. Website owners with limited technical resources struggle to optimize within Google's crawl limits. Mobile users with data caps consume more data for the same content. This creates a regressive system where those with the least resources pay the highest costs.
The Coming Optimization Wave
Splitt's plan to address specific techniques for reducing page size in a future episode signals Google's awareness of the problem. This is not just technical guidance—it is market signaling. When Google's technical leaders publicly discuss optimization techniques, they are setting expectations for the entire web ecosystem.
The opportunity lies in developing more efficient structured data formats that reduce page weight while maintaining machine readability. Optimization tools and services that can reduce page size while maintaining functionality will see growing demand. There is an emerging market for lightweight web solutions targeting regions with slower internet connections or metered data plans—a £50 million opportunity that most Western businesses ignore.
Execution Implications
For executives, this requires specific actions. First, audit page weight against Google's 2 MB crawl limit for critical content. Second, evaluate structured data implementation against actual user experience metrics in target markets. Third, develop separate optimization strategies for high-speed versus emerging markets.
The threat is clear: user experience degradation in slower connection areas creates market exclusion. Potential search ranking impacts if page size affects performance metrics could create sudden visibility drops. The tension between machine-readable structured data and user-facing content efficiency requires strategic prioritization that most businesses have not considered.
The Infrastructure Power Dynamic
What is most revealing is how this debate exposes Google's infrastructure power. By setting crawl limits and defining what constitutes "page weight"—a term Splitt noted lacks consistent definition—Google shapes web development priorities. The flexibility of these limits means Google can privilege certain content types or publishers, creating structural advantages that are not visible to most businesses.
This creates a hidden competitive landscape. Businesses that understand Google's infrastructure priorities and can optimize within its technical boundaries gain advantages. Those that treat page optimization as a technical afterthought risk exclusion from search visibility and user engagement in critical markets.
Source: Search Engine Journal
Rate the Intelligence Signal
Intelligence FAQ
It creates a technical boundary that prioritizes efficient content. Businesses exceeding this limit risk incomplete crawling and reduced search visibility, forcing strategic choices about what content matters most.
Structured data adds invisible weight for machine readability while providing no user benefit. This creates a direct trade-off: better search understanding versus slower page loads, particularly in markets with limited bandwidth.
Emerging markets with slower connections and regions with metered satellite internet suffer most. These users experience degraded performance and higher data costs, creating market exclusion that businesses targeting global growth cannot ignore.
Through strategic prioritization: implement structured data only where it provides clear search benefits, develop separate optimization strategies for different markets, and treat page weight as a competitive metric, not just a technical one.
