Watch the overlay (bottom right) — it shows live per-detector timings on debug
builds with the detectorPerf feature enabled. If it says "waiting for debug events", enable
Debug → Content Scope Scripts Debug State and reload.
Detector scans run on load-time timers (typically 500ms / 1s / 5s after page load),
so page size only matters at load. To make scans slower, reload with a bigger DOM via the URL:
?paragraphs=40000. Change a junk param (e.g. &r=2) each reload to avoid
tab reuse.
Force an on-demand rescan without reloading by opening
"Report Broken Site" from the browser menu — it runs the detectors immediately.
Severe events: when a single run or the combined per-page total crosses the highest
configured threshold edge, a SEVERE entry appears in the overlay and an immediate telemetry pixel
fires natively.
The buttons below grow the DOM in place — useful only before the load timers fire, or ahead of an
on-demand rescan.
Matched detectors retire: auto scans skip a detector after its first match
(first-success), so a matched detector's runs column stops counting while the others keep going.
All URL parameters:
?paragraphs=N&iframes=N&framesrc=real&adwall=1&next=<url>&nextdelay=<ms>
Synthetic workload — iframes (each gets its own C-S-S injection and its own counters)
Synthetic workload — near-miss filler text. Each line shares a prefix with real adwall
phrases, so the text scanners do full work on every node without ever matching. It is meaningless by
design; more lines = slower scans.