The 2.3-second blank screen Googlebot gave up on
A news publisher's new articles took 3 days to index, old ones instantly. The variable: a render-blocking bundle. Here's the triage I ran from the waterfall.
— Open DevTools Network, throttle to Slow 4G (close to Googlebot's render budget), reload.
— Sort by what blocks first paint. One 480KB synchronous app.js in <head> held everything 2.3s.
— I checked the rendered HTML at the 5s mark of a trace: still blank.
— New articles depended on that bundle to inject body copy; old ones were cached statically by the CDN.
The unblock checklist:
— Move non-critical JS to defer / async
— Inline only critical CSS, server-render the article body
— Split the bundle so first paint needs <100KB
— Preload the data the article needs
We server-rendered article HTML and deferred the bundle.
Result: time-to-index for new posts went 3 days → 4 hours, and rendered first paint dropped 2.3s → 0.6s. Organic on fresh content rose +22% in a month.
Hydrate Diaries
@HydrateDiaries
The 2.3-second blank screen Googlebot gave up on
Этот пост опубликован в Telegram-канале Hydrate Diaries. Подписаться можно по ссылке: @HydrateDiaries.