04Performance
Performance Engineering
Fast is an architecture decision, not a plugin.
Overview
We profile the whole request path (browser, JavaScript, images, CDN, origin server, database), find where the milliseconds go, and remove them. Core Web Vitals improve because the causes are gone.
What we do
Capabilities
Frontend
- LCP, INP and CLS
- JavaScript reduction
- Frontend profiling
- Font and render strategy
- Third-party script control
Assets
- Image pipelines
- Modern formats and sizing
- Asset optimization
- Critical resource loading
- Video delivery
Edge
- Caching architecture
- CDN configuration
- Cloudflare tuning
- Cache keys and purging
- Edge rendering
Origin
- Nginx tuning
- OpenLiteSpeed tuning
- PHP and Node runtime tuning
- Database performance
- Query and index fixes
How we approach it
Principles we hold ourselves to
- 01
Profile, don’t guess
Traces, waterfalls, field data and flame charts first. Nothing gets changed until we know where the time goes.
- 02
Delete before you optimize
The fastest JavaScript is the JavaScript that never ships. Removing work beats making work faster.
- 03
Cache on purpose
Explicit cache keys, lifetimes and invalidation. A CDN in front of an uncacheable site is an expensive proxy.
- 04
Keep it fast
Performance budgets in CI and field monitoring after launch, so the site is still fast ten features later.
Signals
You might need this if…
- PageSpeed is red and the fixes haven’t stuck
- Your server struggles under ordinary traffic
- Interactions lag on mid-range phones
- There’s a cache, but nobody trusts it
Works with
- Chrome DevTools
- WebPageTest
- CrUX
- Cloudflare
- Nginx
- OpenLiteSpeed
- Redis
- PostgreSQL / MySQL
Questions
Asked often
Related
Usually works alongside
Bring us the hard part.
Tell us what you’re working on. The people who reply are the people who would build it.