How to Build a Performance-First Agency Culture
Most agencies already say they care about speed. The failure mode is different: performance becomes a one-off audit before launch, a ticket someone opens after a client forwards a bad PageSpeed score, or a single developer's interest instead of a delivery standard.
When the one senior developer who "owns performance" is busy or leaves, the standard slips. Account managers cannot explain LCP in plain language. Designers do not know a hero image can dominate LCP as much as server response time.
Performance-first does not mean every site hits 100 on Lighthouse. It means your team agrees on what "good enough" is for a given client, when you measure it, and who is accountable when a regression ships. Launch checklists include a performance sign-off, not only UAT.
What we standardise first:
Written thresholds by site type (e-commerce, lead-gen, publisher), not a private spreadsheet
Performance in intake, during build, and after launch, not only launch week
Shared visibility: account teams see the same numbers delivery sees
Small rituals that fit existing meetings: a five-minute slot in weekly project review, a no-new-third-party rule in tickets
