Performance as a Feature

Customers pay for fast.

Overview

Performance is product. Customers pay for fast; they leave when the product gets slow. Treating performance as a feature, with explicit SLOs per tier, web-vitals targets per page, and per-feature budgets enforced in CI, makes engineering decisions reflect that reality. Treating performance as something to fix later is how products end up with cohorts of churned customers.

• Customers pay for fast. Speed correlates directly with retention and conversion. Performance is product value.
• Per-tier performance SLO. Tier-1 user journeys carry tighter SLOs than tier-3. Priority shapes the budget.
• Web vitals as product metric. LCP, INP, CLS per page. The user-experience metrics Google ranks against and customers feel directly.
• Per-feature budget plus quarterly review. Each feature has a documented performance budget; quarterly review catches drift before it becomes user-visible.

The approach

Three habits make “performance as feature” real rather than aspirational: per-tier SLOs that engineering can actually enforce, performance budgets in CI, and quarterly review tied to user-experience data.

• Per-tier SLO. Performance SLO matched to user-journey priority. Tier-1 gets the tightest budget.
• Performance budgets enforced in CI. Build fails when the budget is exceeded. Enforcement is automated; nobody has to remember.
• Web vitals as product metric. LCP, INP, CLS per page on the standing dashboard. RUM data is the source of truth.
• Quarterly review plus documented policy. Standing review catches drift; per-team the performance policy lives in the runbook.

Why this compounds

Each enforced budget locks in the current performance and prevents quiet erosion. The team’s product engineering fluency deepens; new features ship with performance budgets on day one rather than getting bolted on after a complaint.

• Customer retention improves. Right performance preserves customers across hundreds of feature releases.
• Engineering culture sharpens. Performance budgets push engineers to think about cost at PR time.
• Operational fit. Right SLO matched to priority. Investment goes where the customer impact is.
• Year-one investment, year-two habit. First SLO is heavy lift. By year two, every new feature ships with a budget.