Performance Sprint: fix your biggest issues in 2 weeks
Most sprints waste the first week figuring out what to fix. We don't.
We install real-user monitoring a month before the sprint starts. By day one, we already know exactly which pages are slow, which devices suffer most, and where the highest impact fixes are. That month of data is what separates a sprint that ships from one that produces a report.
The sprint itself is two weeks of heads-down implementation. We work directly alongside your team to ship improvements and leave a clear backlog for what comes next.
How the sprint works
The sprint has three phases. The first two happen before we arrive.
Phase 1 - Install RUM (month before the sprint)
We install real-user monitoring on your site. One lightweight script that captures Core Web Vitals, page types, device types and connection speeds from actual visitors. No synthetic lab conditions.
One month of data gives us enough signal to prioritise confidently. We're not guessing what to fix on day one. The backlog is already built.
Phase 2 - Backlog review (week before the sprint)
Before the sprint starts we review the RUM data together, prioritise the backlog by impact, and agree on what we're tackling in the two weeks. No surprises, no scope creep.
Phase 3 - The sprint (2 weeks)
We work alongside your team. Each morning: a short sync on what we're fixing and why. We write the fixes, your team reviews and merges. By end of week two you've shipped real improvements. Not a report sitting in a backlog.
- Daily stand-up to keep momentum and remove blockers
- Fixes go through your normal review process
- RUM data tracks gains in real time as changes ship
- Final session: review of results and backlog for what's next
What you get at the end
The sprint is built around output, not deliverables. You ship improvements during the sprint, not after.
A UK fashion retailer saw fast responsive sessions more than double across their product listing pages after a focused three-month engagement. UX Score went from 75 to 100.
Shipped performance improvements
Real fixes merged to production during the two weeks. No document of recommendations sitting in a backlog.
Measurable gains in Core Web Vitals
RUM data tracks the impact of every change as it ships. You can see the improvement in LCP, INP and CLS in real time.
A prioritised backlog for what's next
Not everything gets fixed in two weeks. You leave with a clear, prioritised list of the next highest-impact items to tackle.
RUM monitoring in place
The monitoring stays after the sprint. You can track performance over time and catch regressions before customers notice.
Team capability transfer
Working alongside your team means knowledge transfer happens naturally. Your developers understand the fixes and can apply the same thinking to future changes.
Revenue recovered
Faster pages convert better. The sprint typically recovers more revenue in the first month than it costs - especially on high-traffic e-commerce pages.
Investment
Typically €15,000–€20,000 for a 3–4 week sprint. Scope and complexity of your stack determines the final range. We'll give you a clear quote after an initial conversation.
The sprint is designed to be self-funding: performance gains typically recover more revenue in the first month than the sprint costs.
Sprint slots book out 6 weeks in advance
Because we need 30 days of RUM data before the sprint begins, the earliest we can start is 5–6 weeks after the initial conversation. We run a limited number of sprints at a time, and slots fill on a first-come basis.
Get in touch now and we install the monitoring straight away. By the time the sprint kicks off, we already have a full picture of what to fix.
Why not just ask your agency?
Your agency can work on performance too. Most won't start from real-user data. They'll run Lighthouse, pick the high-scoring recommendations, and hand you a report. You'll spend the first two weeks of any engagement figuring out what actually matters.
We've already done that work before the sprint starts. The month of RUM data is the difference between fixing the right things and fixing the easy things.
FAQ - Performance Sprint
Why do we need RUM monitoring before the sprint?
Because we don't want to guess. Lab tools like Lighthouse test one page in ideal conditions. Real-user monitoring shows you what real visitors on real devices actually experience - which pages are slow, which segments suffer most, and where the biggest gains are. One month of data gives us a solid backlog before the sprint even starts. We're not discovering problems on day one. We're fixing them.
What RUM tool do you use?
We work with whatever makes sense for your setup. We can install a lightweight custom collector, or work with tools you already have - SpeedCurve, Datadog, Sentry, or similar. The key is having event-level data: page type, device, connection, Core Web Vitals. We'll help you set it up correctly if you don't have this yet.
What does the sprint actually look like day-to-day?
We work alongside your team, not separately. Each morning starts with a short sync: what we fixed yesterday, what we're tackling today, any blockers. We write the fixes, your team reviews and merges. By the end of week two you have shipped improvements and a clear picture of what comes next.
How much access do you need to our codebase?
Read access to understand the stack and find root causes. We write fixes and submit them for review - your team merges. We don't need deploy access. Everything goes through your normal review process.
We did the workshop last year. Does the sprint still make sense?
Yes, and it's often the natural next step. The workshop gives your team the skills to understand and triage performance issues. The sprint is where we work together to implement those fixes. It goes faster than tackling them alone, and you have expert support on the hard problems.
What's the investment?
A typical sprint runs 3–4 weeks and puts the investment in the €15,000–€20,000 range depending on scope and complexity. Get in touch and we'll give you a clear quote. The sprint is designed to be self-funding: the performance gains typically generate more revenue than the sprint costs within the first month.
What happens after the sprint?
You'll have shipped real improvements and a prioritised backlog for what comes next. Your RUM monitoring stays in place to track the gains. Some clients continue with periodic check-ins or a follow-up sprint. Others use the momentum to run future improvements themselves - especially if their team has done the workshop.
See it in practice
Not sure what a sprint looks like in practice? Read how a UK fashion retailer improved INP across three major e-commerce brands using the same approach.
Other Services
Not sure a sprint is the right fit? Here's how the other services compare.
Performance Workshop
Build performance expertise in-house. A 2-day intensive that equips your senior developers with the knowledge and tools to fix performance issues themselves.
Performance Audit
A full strategic analysis: real-user data, business case, and a prioritised roadmap. The right fit for complex sites or organisations that need a complete picture before committing to a direction.