Faster, more stable, cheaper to run.
Slow pages cost revenue, technical debt costs many times more later. In the retainer we work continuously on speed and stability — preventively, not in firefighting mode. From 600 €/month on the retainer.
Speed is a feature.
Core Web Vitals directly affect ranking and conversion. We measure, find the real bottlenecks and fix them deliberately — instead of optimising blindly.
- Core Web Vitals: improve LCP, INP and CLS deliberately
- Database and query optimisation as data grows
- Refactoring: keep code maintainable before it slows you down
- Make technical debt visible and reduce it predictably
- Measurable before/after — no gut feeling
Core Web Vitals — when it's good.
Thresholds per Google (Core Web Vitals). We measure with real field data (CrUX) plus Lighthouse.
Where we start.
A typical bottleneck — fixed.
Common questions about optimisation.
01What exactly are LCP, INP and CLS?
LCP (Largest Contentful Paint) measures when the largest visible content has loaded (load feel). INP (Interaction to Next Paint) measures how fast the page responds to clicks/taps (replaced FID in 2024). CLS (Cumulative Layout Shift) measures how much content jumps around while loading. All three are official Google ranking signals.
02Does optimisation really increase revenue?
Often measurably: Google reports clear bounce and conversion effects with every second of load time. We measure before/after with field data (CrUX) and Lighthouse so the effect is provable, not just claimed.
03Which tools do you measure with?
Lighthouse and PageSpeed Insights for lab data, the Chrome UX Report (CrUX) and the web-vitals script for real field data from your users, plus WebPageTest for detailed waterfalls. Field data is decisive — it counts for ranking.
04What is technical debt — and why is it expensive?
Quick fixes from the past that slow down every change today and invite bugs. Left alone they grow exponentially. In the retainer we reduce them in small, tested steps — no risky big-bang rewrite.
05How quickly do you see results?
Typical quick wins (images, caching, render blockers, an N+1 query) take effect right after deploy. Field data (CrUX) needs about 28 days for its rolling average to fully reflect the improvement.
What might still hold you back.
01How do we see that the optimisation actually helps?
We measure before and after — load times, error rates, server costs. You get numbers, not claims; what doesn't measurably improve, we don't do.
02Is optimising worth it or should we rebuild?
Optimising usually wins — targeted at the bottlenecks rather than everything anew. Where technical debt sits too deep, we say so honestly instead of patching endlessly.
03Does the optimisation disrupt live operations?
We work preventively and on staging, deploy in a controlled way — improvements arrive without your users noticing a break.
04Am I tied to the retainer?
No. The retainer runs monthly and is cancellable at short notice. You stay because it gets measurably faster and more stable — not because of a contract.