Why does one test request many files?

The browser loads the resources needed by the page, and StatusCake records timing for each request in the waterfall.

What user agent does the Page Speed test use?

StatusCake has documented `StatusCake_Pagespeed_Indev` as its default, but a customer can set a custom user agent. Inspect the full header used by the test.

Does StatusCake Page Speed respect robots.txt?

The bot record says yes, but StatusCake's Page Speed documentation does not publish a fixed robots token or describe robots handling. Use the test settings for predictable control.

Does StatusCake Page Speed feed AI systems?

No. StatusCake documents it as a performance monitor, with no role in AI search or model training.

StatusCake Page Speed Bot Guide

What is StatusCake Page Speed?

StatusCake Page Speed opens a customer-selected page in a real browser and records how it loads. The test is built for performance monitoring, so it measures the page and reports when configured thresholds are crossed. It does not simply ask whether the server returned a successful status.

A run loads the page's resources and records timing for each one. That can produce a short cluster of requests for the document, images, scripts, styles, and other files, followed by a waterfall in the StatusCake report. StatusCake warns that this uses more bandwidth than a regular HTTP test and recommends monitoring only one or two representative pages per website.

StatusCake has published StatusCake_Pagespeed_Indev as the default page-speed user agent, and customers can configure another value. Tests can also block common trackers, set a viewport, or use connection throttling. The exact request pattern therefore depends on the saved Page Speed settings.

The service reports browser performance to the StatusCake customer. It is not documented as indexing the page for AI search or collecting material for model training. Any search benefit from a faster site is separate from the StatusCake bot's access.

Not relevant for AI search

Is StatusCake Page Speed relevant for AI search?

No. StatusCake Page Speed is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

StatusCake Page Speed runs synthetic monitoring or uptime checks on a schedule. It is not collecting content for any index or model, so it has no bearing on search rankings or AI answers. You usually see it because your own team or a service you use set up a check.

How to handle StatusCake Page Speed

Let the configured page and its required resources load normally if the performance report is still wanted. A WAF block on one script or image can leave the HTML reachable while making the waterfall incomplete or misleading.

Change or remove the Page Speed test in StatusCake when the traffic should stop. The product allows custom user agents, and the bot record does not supply a stable robots token for this test, so there is no dependable Page Speed robots snippet to publish. For an access exception, match the actual configured header and StatusCake's current Page Speed locations, then limit the rule to the pages and resources under test.

Examples

A homepage test loads the HTML, CSS, JavaScript, images, and fonts. StatusCake records the timing of each request in the page's waterfall.
A report suddenly shows a missing script, and the team finds that its WAF challenged the Page Speed browser. It narrows an exception to the configured test source and repeats the run.

Frequently asked questions about StatusCake Page Speed

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

Page Speed loads a page in a browser and times its resources. A StatusCake Uptime test checks whether an endpoint meets its configured availability conditions.