Home InternationalGoogle: Pages Are Getting Larger & It Still Matter...
International⭐ Featured

Google: Pages Are Getting Larger & It Still Matters via @sejournal, @MattGSouthern

Google's Gary Illyes and Martin Splitt discuss page weight growth, the 15MB crawl limit, and whether structured data is adding bloat to web pages. The post Google: Pages Are Getting Larger & It Still Matters appeared first on Search Engine Journal .

6 April 2026 at 08:20 pm
1 views
Google: Pages Are Getting Larger & It Still Matters via @sejournal, @MattGSouthern

In a recent discussion on Twitter, Google's Gary Illyes and Martin Splitt shed light on the growing size of web pages and its implications for search engine optimization (SEO). The conversation centered around the 15MB crawl limit imposed by Google and whether structured data is contributing to the bloat of web pages. This topic has been of significant interest to the SEO community, as page weight can impact both user experience and search engine rankings.

Gary Illyes, a well-known engineer at Google, has previously spoken about the 15MB crawl budget, which refers to the maximum amount of data that Googlebot, Google's crawler, can consume from a single page. This limit is in place to prevent overly large pages from consuming excessive server resources and slowing down the crawling process. However, Illyes noted that the average page size has been increasing over time, with some pages now exceeding the 15MB threshold. This trend raises concerns about the efficiency of crawling and the potential impact on SEO.

Martin Splitt, another Google engineer, chimed in to discuss the role of structured data in this context. Structured data, which includes elements like schema markup, is designed to provide search engines with additional context about the content on a web page. While this can be beneficial for understanding and ranking pages, there are concerns that the inclusion of structured data might be contributing to the overall size of web pages. Splitt acknowledged that structured data can add some overhead, but emphasized that its benefits often outweigh the costs.

The discussion also touched upon the broader implications of larger pages for user experience. As pages grow in size, they can become slower to load, which can lead to higher bounce rates and a poorer user experience. This, in turn, can negatively impact SEO, as search engines increasingly prioritize user experience in their ranking algorithms. Therefore, there is a need for web developers and SEO professionals to find a balance between providing rich, structured content and keeping page sizes manageable.

One potential solution to address the growing page sizes is the adoption of progressive enhancement techniques. This approach involves building lightweight, mobile-first pages that load quickly, while also providing additional content and functionality for users with faster connections or more advanced devices. This not only improves user experience but also helps to keep page sizes under control, making them more crawl-efficient for search engines.

Another angle to consider is the impact of larger pages on server resources and performance. As more pages approach or exceed the 15MB crawl limit, there may be increased demand on servers to handle the load. This can lead to slower response times and potential issues with server capacity. To mitigate these challenges, web developers may need to optimize their content delivery and consider strategies like content delivery networks (CDNs) or compression techniques to reduce page size without sacrificing essential content.

In conclusion, the growing size of web pages and the 15MB crawl limit imposed by Google are significant issues that warrant attention from the SEO and web development communities. While structured data can add value by providing search engines with additional context, its contribution to page bloat must be carefully managed. By focusing on user experience, adopting progressive enhancement techniques, and optimizing server resources, it is possible to create web pages that are both crawl-efficient and effective in delivering value to both users and search engines. As the conversation between Gary Illyes and Martin Splitt highlights, the challenge of balancing page weight and SEO is an ongoing one that requires thoughtful consideration and strategic planning.

📰 Related News
Ollama 0.2.6 Released with Native Gemma 4 Support and Enhanced Performance
Ollama 0.2.6 Released with Native Gemma 4 Support and Enhanced Performance
Ollama 0.2.6 is now live, featuring native support for Google's Gemma 4 models and improved local inference performance for Windows, macOS, and Linux.
14 Apr
Weekly news roundup: Shortages spread to MLCCs; SK Hynix reportedly in talks with Microsoft and Google
Weekly news roundup: Shortages spread to MLCCs; SK Hynix reportedly in talks with Microsoft and Google
Below are the most-read DIGITIMES Asia stories from the week of April 6-April 13, 2026:
14 Apr
cutile-stencil 0.2.0
cutile-stencil 0.2.0
An xDSL-based stencil compiler that generates optimized GPU kernels via NVIDIA cuTile
14 Apr
merlin-llm added to PyPI
merlin-llm added to PyPI
Merlin — a fast local LLM for agentic coding on Apple Silicon
14 Apr
Fluent Cut - Craft and compose videos programmatically in PHP with an elegant fluent API
Fluent Cut - Craft and compose videos programmatically in PHP with an elegant fluent API
Craft and compose videos programmatically in PHP with an elegant fluent API - b7s/fluentcut
14 Apr
Crypto Investor at Center of Trump Corruption Allegations Now Sees Himself as ‘Victim’
Crypto Investor at Center of Trump Corruption Allegations Now Sees Himself as ‘Victim’
Justin Sun has accused Trump-affiliated World Liberty Financial of misconduct and a general lack of transparency.
14 Apr
nvidia-nat-weave 1.7.0a20260413
nvidia-nat-weave 1.7.0a20260413
Subpackage for Weave integration in NeMo Agent Toolkit
14 Apr
nvidia-nat-s3 1.7.0a20260413
nvidia-nat-s3 1.7.0a20260413
Subpackage for S3-compatible integration in NeMo Agent Toolkit
14 Apr
Social Security Trust Fund to Run Dry in 2032: Just 6 Years From Now
Social Security Trust Fund to Run Dry in 2032: Just 6 Years From Now
Six years. That is how much time separates retirees from a Social Security system that, by its own projections, runs out of money. If you are 56 years old...
14 Apr
cane-gpu-perf added to PyPI
cane-gpu-perf added to PyPI
GPU inference benchmarking with opinionated diagnostics
13 Apr