DISCIPLINE 05 · PERFORMANCE
Performance Optimization
Measured work against real bottlenecks. Bundle splitting, query tuning, caching, monitoring.
DURATION
2–6 weeks
GATES
4 phases
ENGAGEMENT
Fixed scope
STACK
Vite · Lighthouse · Redis
What you get
Six artefacts, all of them yours on delivery. No phase closes without its output.
- 01Baseline measurement across the flows that matter, before any change
- 02Ranked list of bottlenecks with the expected gain for each
- 03Bundle, query and caching changes shipped one at a time, each measured
- 04Performance budget wired into CI so regressions fail the build
- 05Before-and-after report with the numbers that moved
- 06Handover session recorded, with the monitoring left in place
Tooling
FRONTEND
Lighthouse CI, WebPageTest, bundle analysis per route
BACKEND
OpenTelemetry traces, flame graphs, p95 per endpoint
DATA
EXPLAIN ANALYZE, index review, connection pool sizing
CACHING
Redis, HTTP cache headers, CDN configuration
MONITORING
Real-user metrics, alert thresholds, weekly report
Timeline
01
Discovery
1 WEEKMeasure everything, change nothing
02
Architecture
1 WEEKRank by gain over effort, agree targets
03
Delivery
1–4 WEEKSOne change per deploy, measured against the baseline
04
Operate
ONGOINGBudget enforcement, regression alerts, quarterly review
WHEN NOT TO USE THIS
Nothing has been measured yet and the instinct is a rewrite. Measure first; it is usually cheaper.
The slow part is a third-party you cannot change. We will tell you in the first week.
You want a new feature, not a faster one. That is FULL-STACK.