<b>The page that was too heavy for Google to finish rendering</b>

<b>The page that was too heavy for Google to finish rendering</b>

A comparison site had long, content-rich pages that ranked beautifully — for the top third. Anything past the midpoint never ranked, never earned a snippet, as if the lower half didn't exist.

It didn't, to Google. The pages shipped a 2.8MB JavaScript bundle that built the entire DOM client-side, including all the content. Googlebot's renderer has resource limits; on heavy pages it can stop executing scripts before the full DOM is constructed. Our pages took 14+ seconds of main-thread work to fully build. The crawler captured the DOM at the point its render budget expired — roughly the top third — and indexed only what had mounted by then.

The content was identical top to bottom in the source data. The crawler simply never reached the rest.

We server-rendered the full article HTML and used the JS only for interactivity, dropping the critical bundle to 180KB.

—Page captured by Googlebot: 35% → 100% of DOM
—Mid-page and footer keywords ranking: 8 → 240 in 12 weeks

Googlebot doesn't wait forever. A bloated client bundle means it indexes whatever rendered before the timer ran out.