Help & FAQ
Common questions about website analysis
Quick Answers
Why did my scan fail?
What can I try?
Is this just your tool?
What sites commonly fail?
Frequently Asked Questions
Web auditing tools like ours work by making automated HTTP requests to websites and analyzing the responses. However, many websites implement security measures specifically designed to block or slow down automated requests:
- Web Application Firewalls (WAF) - Services like Cloudflare, Akamai, and AWS WAF detect and block automated traffic patterns
- Bot Protection - CAPTCHA challenges, JavaScript challenges, and behavioral analysis that automated tools cannot pass
- Rate Limiting - Servers that restrict how many requests can be made from a single source in a given time period
- IP Blocking - Some sites block entire ranges of IP addresses associated with cloud hosting providers
- Geographic Restrictions - Sites that only allow access from certain countries or regions
These security measures are legitimate and important for protecting websites from malicious bots, scrapers, and DDoS attacks. Our scanner respects these protections and will not attempt to bypass them.
If a scan fails, here are some things you can try:
- Try a simpler URL - Scan the homepage (e.g., example.com) instead of a deep page (e.g., example.com/products/category/item)
- Wait and retry - Some rate limits reset after a few minutes. Wait 2-5 minutes and try again
- Try with/without www - Some sites behave differently with "www.example.com" vs "example.com"
- Check if the site is accessible - Try visiting the site in your browser to make sure it's actually online
- Verify the URL - Make sure there are no typos in the domain name
Important
Timing & Limits Reference
The hard limits a scan runs under. If an audit stopped earlier than you expected, or covered less of your site than you expected, the reason is usually one of these.
| Rule | Value |
|---|---|
| Cooldown between scans | 60 seconds |
| PageSpeed phase budget | 90 seconds |
| Orchestrator max duration | 300 seconds |
| Stale session threshold | 45 seconds without a heartbeat |
| Polling pause | After 5 consecutive network errors |
| Core phase poll interval | 2 seconds |
| PageSpeed phase poll interval | 5 seconds |
| Max links checked per scan | 50 |
| Max pages crawled per scan | 20 |
| Max redirect hops followed | 5 |
| Oversized image threshold | 300KB |
| Recent audits kept in cache | 10 (oldest evicted first) |
| Scan session retention | 7 days |
Per-analyzer network budgets — how long each individual check waits before giving up — are listed in the analyzer reference.
Additional Resources
- Terms of Service - Usage guidelines and limitations
- Privacy Policy - How we handle your data
- PageSpeed Insights API Documentation
Still Have Questions?
If your question isn't answered here, contact us at support@webauditsuite.com.