How fast does my site need to be for AI agents?
We time our homepage request from first byte to last byte and record the milliseconds.
What it is
This is one uncached request for the HTML document, timed end to end. It does not include images, fonts or scripts, and it is not a page-speed score.
Under 2500 ms is a Pass and above it is a Warning. Where we received no response at all, the Check is recorded as Not evaluated rather than guessed.
It is a single sample from our network, so treat it as an indication and not a benchmark. A repeated Scan is the cheapest way to see whether a number was an outlier.
Why an agent needs it
Agents run under their own timeouts and fetch many pages in a run. A slow document is often abandoned rather than retried.
Slow HTML is also the symptom that travels. A homepage taking 4 s to build usually means the rest of the site does too.
The Fix
Serve the HTML document from a cache or a CDN edge, so a request does not wait on a database query and a template render.
Look at what the page does before it can send its first byte. Blocking API calls during render are the usual cause on small business sites.
Keep the document itself modest. A 900 KB HTML page carrying inlined data takes time to transfer whatever your server does.
This one is a change in your own markup or edge configuration, so the Fix Pack cannot write it for you. A Report names every page it affects, with the Evidence.