Performance optimisation
I find what really slows down your site, store or API — and fix it in order of biggest gain. Every change is measured before and after.
Sound familiar?
Red Core Web Vitals in Search Console and ranking drops.
The API gets slower as data grows.
Cloud bills grow faster than traffic.
Nobody knows where the bottleneck is — no metrics.
What it usually looks like inside
- BrowserRUM · web-vitals
- CDNBrotli · AVIF · HTTP/3Appcode split · SSR/SSG
- Cachestale-while-revalidateDatabaseindexes · EXPLAIN
- Lighthouse CIperformance budgetMonitoringCWV · p95 · alerts
The scope you get
Prioritised audit
A report with issues ranked by impact and cost to fix.
Front-end
LCP, INP, CLS: images, fonts, critical CSS, code splitting.
Backend & SQL
Profiling, indexes, N+1, caching, queues for heavy jobs.
Infrastructure
CDN, compression, HTTP/3, scaling and cost reduction.
Monitoring
RUM, p95 dashboards and alerts so the problem doesn’t return.
Budget in CI
Automated performance tests that block regressions.
Technologies in this area
- Node.js
- PostgreSQL
- Redis
- Grafana
- GH Actions
- Cloudflare
Performance optimisation — FAQ
01How long does an audit take?
Usually 3–5 business days. You get a prioritised report with an estimate for each fix.
02Do you implement the fixes?
Yes, or I hand them to your team with instructions and code review.
03Do you guarantee results?
We agree a measurable goal upfront and I report progress on production data, not just Lighthouse.
Got a project that has to be fast and work at scale?
Describe it in 2 minutes. I'll reply within 24 hours with first insights and a proposed next step.