Scheduled & Automatic Scans

PerfLeaf can run scans automatically so you always have up-to-date performance data without triggering them manually.

Scan frequency

In Site Settings → Crawl Settings, set the Frequency field:

Option	Description
none	No automatic scheduling — manual only
weekly	One scan per week
monthly	One scan per month

The scheduler runs automatically in the background. You don’t need to keep the browser open.

Commit-triggered scans (GitHub)

If you’ve connected a GitHub repository to your site, PerfLeaf can trigger a scan automatically every time a new commit is pushed to your monitored branch.

How it works

1. PerfLeaf polls your repository every 5 minutes for new commits.
2. When a new commit SHA is detected, a scan is queued automatically.
3. The report is tagged with trigger type commit so you can identify it in the reports list.
4. The lastCommitSha on your site record is updated after each triggered scan.

Scan delay

You can set a GitHub Scan Delay in Site Settings (in seconds). This delays the scan after a commit is detected, useful if your deployment pipeline takes time to publish the new version before PerfLeaf should crawl.

Requirements

• A GitHub repository must be connected to the site. See GitHub Integration.
• The Trigger on Commit option must be enabled in Crawl Settings.

Tip

Use the scan delay to give your CI/CD pipeline time to finish deploying before PerfLeaf runs the scan. For example, set a 5-minute delay if your deployment takes around that long.

Viewing automatic scan reports

Automatic reports appear in the site detail page alongside manual ones. The trigger badge (schedule or commit) distinguishes them from manually started reports.