Running a Scan
Crawl limits & politeness
Several settings keep a scan from stressing your own hosting:
- Max pages — hard cap on how many URLs a run will fetch (default 50).
- HTTP timeout — seconds to wait for each page (default 15; a browser-triggered scan caps each fetch at about 8 seconds).
- Requests per minute — throttle so the crawler stays polite on shared or low-resource hosting.
- Overall budget — a scan started from the browser stops after roughly 40 seconds and returns a partial result, so it never outruns the web server’s own timeout. A CLI scan has no overall cap.
On modest hosting, start with a low page cap, then raise it once you see a run finish comfortably.
