How slow is too slow for an AI assistant fetching my page?
An AI assistant that fetches a page while a person waits for the answer does not wait long. If your page is slow to arrive, it may be skipped in favour of something that is not. We time one fetch of your page and tell you where it landed.
What it actually is
It is the time from asking for your page to holding all of its HTML, measured from our server, in the same request we make to read the page for every other check. It includes any redirects on the way, because a visitor pays for those too. It does not measure how quickly the page looks finished in a browser, which is a different thing and has its own section in the report.
Why it matters
When someone asks an assistant a question, it may fetch pages live to answer. The one published test we found put the point at which ChatGPT's fetcher gives up at a few seconds, after which it went elsewhere. A page that is late is a page that was not read, and in an answer engine that is the same as not being there.
What good looks like
A page whose HTML arrives promptly, from a server that does not need a long warm-up, with redirects kept to the few that are needed. Large pages take longer simply because there is more to send, so a lean document helps here too.
Being honest about it
Treat this as a hint. It is a single fetch from one place at one moment, so a slow result can be a cold start or a busy minute, and a fast one does not prove your server copes under load. The evidence for a give-up point is one vendor's controlled test on one new domain, and we have not seen it repeated, which is why the check counts for only a small part of the score. We do not show a time threshold in the result, only the verdict.
Where most sites go wrong
Pages built on demand with nothing cached, so every request waits for the server to assemble the page; long chains of redirects before the real page; and heavy documents that take seconds just to send. A slow first visit after the site has been idle is also common, and it is exactly the visit a live assistant makes.
On the web
In October 2026, 89% of the sites we scanned passed the “Your page arrives quickly” check.
| Result | Share of sites |
|---|---|
| Pass | 89% |
| Worth a look | 7% |
| To fix | 4% |
| Couldn't judge | 0% |
Webflow sites pass it most often, at 94%. WordPress sites pass it least often, at 72%.
Goes with
- Sites that pass this are 4 times as likely to pass the “Resource-discovery Link headers” check too.
- Sites that pass this are 3.5 times as likely to pass the “Core security headers are set” check too.
Not enough history yet.
Based on the sites Bot Appétit has scanned: ones people chose to scan, plus lists we scan for research. Not a random sample of the web.
Not sure where yours stands?
A free scan checks this and everything else in about 20 seconds — no signup. Or if it's already flagged and you'd rather it were simply handled, we do that too.
Flagged for this one? We handle it. No pitch, just a plain-English chat.
Book a call