Googlebot's rendering limit is not 5 seconds: it is the Event Loop

This week a developer at a client told me they were cutting features from a page because "Google stops rendering after 5 seconds". It is a line I have been hearing for years. And it is not true.

Dave Smart's test on Google's Web Rendering Service

Dave Smart, from Tame the Bots, published the test that proves it on 23 July 2026. He built a page with two API calls that each take between 3 and 6 seconds to respond from the server. Total: between 6 and 12 seconds. Google rendered and indexed the full content, both in URL inspection and in actual indexing.

Where does the myth that Google stops rendering after 5 seconds come from?

Google's Web Rendering Service does not use the hardware clock. It uses a virtual clock that can speed up, slow down or freeze. When the WRS waits on a network request, it freezes time. That is why, if you set up a counter with setInterval inside your page, it stops at 5 and you conclude there is a 5-second limit. What you are really measuring is a clock that does not advance while Google works.

The rendering test data that confirms the myth is false

• In the test, two calls that took 9 real seconds of server time reported a total time of 0.02 seconds.
• In actual indexing, the clock always starts at midnight UTC, so every timestamp comes out as 00:00:00.

So is there any limit to Google's rendering?

Yes, but it is not a time limit. Google watches the Event Loop to decide when the page is idle. Smart built a page with requests in an infinite loop: the live tool cut off at 16-18 calls (48-54 seconds) and actual indexing at 10 (30 seconds).

My take on the Web Rendering Service rendering limits

My reading, after seeing how many teams have rewritten architectures chasing this threshold: the problem is never the clock, it is the Event Loop. If you have constant polling, infinite animations or listeners that reactivate on their own, then you do have something to fix. If not, stop optimizing against a made-up number and optimize for the user, who has far less patience than Googlebot.