Wolfix runs in two modes. A quick scan gives you a fast read on the gaps that block launch. A deep scan adds the dynamic and provider checks that need a full page render and network round-trips. Both feed the same report — the difference is how much of your project Wolfix inspects and how long it takes.
What each mode inspects
The two modes draw from the same six-step pipeline. A quick scan runs the deterministic, fetch-based steps. A deep scan adds the steps that boot a headless browser and query your providers.
Quick scan
Static URL fetch (legal pages, OG tags, robots.txt, footer links), code-signal detection, and regulatory mapping. No headless browser, no provider calls.
Deep scan
Everything in a quick scan plus the dynamic URL render (cookie consent, JS-injected scripts), DNS records (SPF, DKIM, DMARC, MX), and provider checks (account type, email deliverability).
The split maps directly onto the scan pipeline. The first three steps — code scan, static URL scan, and regulatory mapping — read source signals and plain HTTP responses, so they finish in seconds. The last three — dynamic URL scan, DNS checks, and provider checks — depend on a rendered page and external lookups, which is why they only run in a deep scan.
How long each takes
Severity scale
The severity scale above is what both modes produce — every finding lands in one of the four tiers regardless of how it was detected. What changes between modes is coverage, not severity.
| Mode | Pipeline steps | Typical duration | Headless browser | | --- | --- | --- | --- | | Quick scan | Code, static URL, regulatory mapping | 10–30 seconds | No | | Deep scan | All six steps | 30–90 seconds | Yes |
A quick scan is fetch-and-parse only, so it returns almost immediately. A deep scan adds a full page render plus DNS and provider round-trips, which is where the extra time goes.
Both modes share one report
A quick scan and a deep scan write to the same report structure. A deep scan simply fills in the findings a quick scan cannot see — it does not relabel or re-score anything the quick scan already found.
When to reach for each
Pick the mode by what you are trying to learn.
Use a quick scan when
- You just connected a project and want a fast read on launch blockers.
- You changed a legal page or your robots.txt and want to confirm Wolfix picks it up.
- You are iterating quickly and only care about the document- and code-level gaps.
Use a deep scan when
- You are preparing to charge your first customer and need the full picture.
- Your gaps involve cookie consent, JS-injected trackers, or anything that only appears after the page renders.
- You changed DNS records or email configuration and want SPF, DKIM, DMARC, and MX re-checked.
Start quick, finish deep
A good rhythm is a quick scan while you build and a deep scan before launch. The quick scan keeps you honest on blockers; the deep scan catches the render-time and provider gaps that only matter once real users arrive.
What neither mode does
Both modes are read-only. Wolfix inspects your project — it never changes your code, DNS, or provider settings during a scan. Fixes happen separately, from the report, where you choose to generate an asset, copy a code-fix prompt, or follow a referral.