Product

Website Performance Engineer

Start with Website URL + key pages. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.

Start with Start with your sources Try the demo

1/wkEvidence reports

FactoriesStart with your sources

IdleIllustrative run

Walking critical flows onapp.example.com

src/server/cart/summary.ts

Flows walked: 0
Draft pull requests: 0

Draft pull requestfix/checkout-summary-no-discount into your default branch

Fix checkout summary for carts with no discount

Integrations

0 integrations

Get started with Website Performance Engineer

Pick an example, connect your tools, and review the first run.

Use template Try the demo

Set up the Website Performance Engineer agent template for this project. Follow /SKILL.md for the exact CLI commands. Goal: Repeat measured loading scenarios, investigate resource and request-chain regressions, and deliver specific improvements with before-and-after evidence when changes can be tested. 1. Install the CLI if it is not on PATH, check that I am signed in, and select my team and project. 2. List the first-party workflow templates. If `website-performance-engineer` is listed, instantiate it with `--path.slug website-performance-engineer` and start the run; otherwise create a project from this template at /new?template=website-performance-engineer&preset=trial. 3. Share the run id, follow the run until it finishes, and summarize its outputs and changes. Ask me before spending FTAI or changing anything outside this repository.

Launch from Claude Code, Codex, Cursor, and other agents.

Related solutions

Integrations

Get started with Website Performance Engineer