HTML Document Over 15MB: Google's Crawl Limit and How to Fix It

What this means

This issue means the raw HTML document for one URL is larger than 15MB. That is the byte size of the HTML response itself, before Googlebot fetches any of the images, scripts, stylesheets, or fonts the page references. Google states that Googlebot fetches up to the first 15MB of an HTML or text-based file, then stops reading that single resource. Referenced files like images, CSS, and JavaScript are requested separately and do not count toward this document's 15MB.

For context, Google notes the median HTML file is about 30 kilobytes, roughly 500 times smaller than this limit. A page that hits 15MB of pure markup is almost always carrying something it should not: thousands of inline base64 images, a runaway server-rendered list, a giant inline data blob, or a script bundle that belongs in an external file.

Why it matters (the 15MB rule)

Google's documented behavior is simple: Googlebot downloads the bytes of the HTML file and, if that file exceeds 15MB, it keeps the first 15MB and discards the rest of that response. Whatever markup sits beyond the cutoff, including headings, body copy, links, and structured data, is never parsed for that URL. If your primary content, internal links, or schema live in the tail of a bloated document, Google may simply not see them.

One reassuring detail: the limit applies only to the initial HTML response, not to the resources it references. Images and videos are fetched as their own requests, so a media-heavy page is not automatically at risk. The danger is markup bloat, content and data baked directly into the HTML, which also wastes crawl capacity and slows rendering. If crawl efficiency matters for your site, see our guide on crawl budget and when you should actually care.

How it gets flagged

During a crawl, SEO ProCheck measures the byte size of each HTML response it downloads, and flags any single document over 15MB. This mirrors how desktop crawlers like Screaming Frog and Sitebulb report response size: they record the size of every fetched document, so an outlier stands out against the typical 30KB to few-hundred-KB baseline. The flag is about the HTML file alone, not the total page weight once images and scripts load.

How to fix it

The goal is to get the HTML response comfortably under 15MB. Work through these in order of likely impact:

• Strip inline base64 data. Images and fonts encoded as data: URIs in the markup are the most common cause. Move them to real files and reference them by URL so they load as separate resources.
• Trim oversized inline SVG. Large unoptimized inline SVG can add megabytes. Externalize it, or run it through an SVG optimizer and reference it with img or use.
• Move bloated inline scripts and styles out. Large inline <script> and <style> blocks, including inlined JSON data dumps, belong in external files. For how Google renders script-heavy pages, see our JavaScript SEO and rendering guide.
• Paginate or split enormous pages. A single page rendering tens of thousands of rows, comments, or products rarely serves users or crawlers. Break it into paginated views.
• Lazy-load below-the-fold content. Load long lists and media on demand instead of dumping the entire dataset into the initial HTML. A lighter document also helps your Largest Contentful Paint.
• Remove duplicated or generated markup. Templating bugs sometimes repeat sections or leak large hidden blocks. Audit the source for accidental repetition.

After changes, re-crawl the URL and confirm the HTML response size has dropped well below the limit.

FAQ