Skip to main content

Help & FAQ

Common questions about website analysis

Quick Answers

Why did my scan fail?

Many sites use security measures (WAF, bot protection) that block automated scanners. This is expected behavior, not a bug.

What can I try?

Try a simpler URL (homepage vs deep page), wait a few minutes and retry, or try without "www" prefix.

Is this just your tool?

No. All web auditing tools (Lighthouse, Ahrefs, SEMrush, Screaming Frog) face the same limitations with protected sites.

What sites commonly fail?

Government sites, banking portals, healthcare systems, large enterprise sites, and sites behind Cloudflare/Akamai protection.

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:

  1. Try a simpler URL - Scan the homepage (e.g., example.com) instead of a deep page (e.g., example.com/products/category/item)
  2. Wait and retry - Some rate limits reset after a few minutes. Wait 2-5 minutes and try again
  3. Try with/without www - Some sites behave differently with "www.example.com" vs "example.com"
  4. Check if the site is accessible - Try visiting the site in your browser to make sure it's actually online
  5. Verify the URL - Make sure there are no typos in the domain name

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.

RuleValue
Cooldown between scans60 seconds
PageSpeed phase budget90 seconds
Orchestrator max duration300 seconds
Stale session threshold45 seconds without a heartbeat
Polling pauseAfter 5 consecutive network errors
Core phase poll interval2 seconds
PageSpeed phase poll interval5 seconds
Max links checked per scan50
Max pages crawled per scan20
Max redirect hops followed5
Oversized image threshold300KB
Recent audits kept in cache10 (oldest evicted first)
Scan session retention7 days

Per-analyzer network budgets — how long each individual check waits before giving up — are listed in the analyzer reference.

Additional Resources

Still Have Questions?

If your question isn't answered here, contact us at support@webauditsuite.com.