render budget
Also called: rendering budget, javascript rendering budget
Render budget is the informal term for the finite CPU time and compute Google spends executing a page's JavaScript before indexing it. Unlike crawl budget (how many URLs Google fetches), it governs how many JavaScript-dependent pages actually get rendered so their content can be read.
Google does not publish an official “render budget” metric. The phrase, popularized by technical SEO teams like Botify, names a real behavior: Google processes JavaScript pages in three phases (crawl, render, index), and rendering is deferred. Google’s own documentation says a page “may stay on this queue for a few seconds, but it can take longer than that. Once Google’s resources allow, a headless Chromium renders the page.” That “once resources allow” is the budget in practice.
Why it is separate from crawl budget
Crawl budget decides which URLs Googlebot fetches. Render budget decides which of those pages get their JavaScript executed. A URL can be crawled, sit in the render queue, and have its client-side content indexed late or incompletely. If your <title>, main copy, or links only appear after JS runs, they depend entirely on that render step.
The old fear (pages waiting weeks to render) has eased. A 2024 Vercel study of 100,000+ Googlebot fetches found Google attempted to render effectively every HTML page, with a median crawl-to-render delay near 10 seconds and the 25th percentile under 4 seconds. The tail is still long (90th percentile in hours), so on large JavaScript sites render lag is a real indexing risk rather than a routine blocker.
The durable fix is not chasing a budget number. It is reducing how much Google has to render: server-side rendering (SSR), static pre-rendering, or shipping critical content and links in the initial HTML so indexing does not wait on the queue.
How it affects your traffic
If your key content only exists after JavaScript executes, any page that renders late or fails to render is not in the index, so it cannot earn clicks. This shows up as pages Google has crawled but left thin or unindexed, and it is easy to miss because the page looks fine in a browser. A technical SEO audit checks the raw HTML Google sees first, flags content that depends on rendering, and moves the critical parts (titles, copy, internal links, schema) into server-rendered HTML so indexing does not wait on the render queue.
Get Technical SEO that moves the needle
We turn terms like this into ranked pages and qualified pipeline. Start with a free Initial SEO Strategy.