# Run the performance audit on one key route and land its top finding

An audit run once against a real route, with its highest-impact finding actually fixed.

Category: Audits and budgets
Source: https://letsship.ai/use-cases/run-the-performance-audit-on-one-route
Published: 2026-08-25

## Goal

Run the performance audit against one route and fix its highest-impact finding.

## Acceptance criteria

- The audit output is attached before and after
- The top finding by impact is fixed
- The score improvement is measured on the same conditions
- Remaining findings are listed for follow-up tickets

## What lands as proof

Two audit runs under identical conditions, so the improvement is attributable rather than incidental.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Fix the top performance finding on {route}

Description: Run the performance audit against one route and fix its highest-impact finding.

Acceptance criteria:
- The audit output is attached before and after
- The top finding by impact is fixed
- The score improvement is measured on the same conditions
- Remaining findings are listed for follow-up tickets

Before you create the issue, run the performance audit against this repository's routes and replace {route} with the worst-scoring one that matters.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: run the performance audit against one route and fix its highest-impact finding. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.

### How do I know the work is done?

The pull request carries the evidence, not only the diff. Here that means score before and after, with the audit output attached, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.