Starting a Scan
Triggering a manual scan
Section titled “Triggering a manual scan”You can start a scan in two places:
- Sites list — click Start Scan on any site card.
- Site detail page — click the Start New Scan button.
The scan is queued immediately and the status changes to In Progress.
What the crawler does
Section titled “What the crawler does”For each page it visits, the crawler collects:
- Core Web Vitals (LCP, CLS, INP, FCP, TTFB) via a real headless browser
- Asset sizes (JS, CSS, images, total payload)
- Accessibility violations (automated WCAG scan)
- Security headers and HTTPS status
- DOM structure metrics
- CO₂ emission estimate
- Page screenshot
- Detected tech stack
Monitoring progress
Section titled “Monitoring progress”While a scan is running:
- A progress bar appears on the site card and site detail page.
- The progress bar shows the percentage of pages processed.
- The status badge shows In Progress.
- You can navigate away — progress is tracked in the background and reconnects when you return.
Cancelling a scan
Section titled “Cancelling a scan”If you want to stop a scan before it completes:
- Go to the site detail page.
- Click Cancel Scan next to the in-progress report.
The report will be marked as Cancelled and partial data will not be used in trends.
Scan triggers
Section titled “Scan triggers”The trigger type is recorded on each report and shown in the UI:
| Trigger | Description |
|---|---|
manual | Started by you from the dashboard |
schedule | Started automatically by the scheduler |
commit | Started automatically when a GitHub commit was detected |