Projects & trends
Group runs of the same page into a timeline, watch five key metrics, and alert on regressions.
What a project is#
A project groups analyses of the same page into a timeline. Runs are keyed by the page's normalized URL (query string ignored), so re-analyzing /checkout next week lands on the same timeline as today's run — whether it arrived by upload, capture, or a monitor.
Trend metrics & delta badges#
Five metrics are tracked per page, each with its own sparkline and delta badge:
| Metric | Better when |
|---|---|
| Performance score | higher |
| Total transfer bytes | lower |
| JavaScript bytes | lower |
| Third-party transfer bytes | lower |
| Page load time | lower |
A delta badge compares the latest run to the one before it (with a percentage where meaningful) and is classified improved / regressed / flat by the metric's direction — a rising score is green, rising bytes are not. The timeline links every point back to its full report.
Regression alerts#
Projects can alert when the newest run regresses against the previous one — a score drop of at least your threshold in points, or total payload growing by at least your threshold percentage. Breaches post a Slack-compatible message to the project's webhook (or the deployment-wide ALERT_WEBHOOK_URL) and/or email a plain-text alert to the project's configured address — set either, both, or neither when creating a project. Alerts are fire-and-forget: a webhook hiccup or a bounced email never blocks or fails the analysis itself.
Monitors build trends automatically#
Adding a monitor offers a "Track trends & alerts" option, checked by default. Leave it on and Harpoon reuses (or creates) a project named after the monitored page, so every scheduled scan lands on that project's timeline and can trigger its regression alerts — no separate project setup required. Uncheck it, or pick a different existing project from the list, if you'd rather manage the attachment yourself.
Turning findings into tickets#
- Any analysis can generate ticket payloads from its recommendations — priority maps from
P0–P3, effort becomes a label. - With Jira or Linear credentials configured server-side, tickets can be created directly; otherwise you get the provider-neutral payloads to file wherever you track work.