01 // audit
5-day stack audit
We profile CrUX data, server traces, and client JavaScript to explain why mobile INP and LCP miss their targets. The report ranks root causes by revenue impact and includes remediation steps.
(02)
five days, in order
Five days, €3,500, and a written roadmap.
[01] · day 01
the data pull
Chrome User Experience Report data segmented by device and route, real-user traces, and your hosting bill down to the line item.
[02] · day 02
the bundle map
Every kilobyte of client JavaScript mapped to its island or route, with hydration overhead and unused framework code flagged for removal.
[03] · day 03
the server traces
API waterfalls, edge cache hit ratios, and serverless cold starts traced down to individual routes and headers.
[04] · day 04
ranked by revenue
We rank findings by revenue impact and effort. The highest-cost bottleneck comes first.
[05] · day 05
the roadmap review
A working session to review remediation steps, effort estimates, and the scope of a migration sprint or fractional pod.
(03)
audit deliverables
You keep the report whether or not you hire us to implement the fixes.
(01) Core Web Vitals diagnostic
CrUX field data for your key templates, split by device and route.
(02) Hydration and bundle map
Every payload traced to its source, with exact removal targets and the kilobytes each is worth.
(03) Server-side trace report
TTFB, edge cache hit ratios, API waterfalls, and cold starts — down to the header.
(04) Prioritized remediation roadmap
Ranked by revenue impact, with PR-ready steps and effort estimates your team can ship immediately.
(04) · the price
one audit, flat fee
The audit costs €3,500. Sign a migration sprint within 30 days and we credit the full fee.
The fractional systems pod
Continuous bi-weekly sprints — content modeling, performance, integrations, edge and cache. Capped at three clients.
The one-time build
A clean replatform to Storyblok + Astro + Cloudflare — the setup the pod then takes over.
(05)
scope and handoff
The audit produces findings and a roadmap; implementation is scoped separately.
(01) root-cause findings
We trace each finding to its source and include a remediation step.
(02) browser to backend
We profile the browser, edge, and backend in one audit.
(03) implementation scope
The audit ends with a written roadmap. Sign a migration sprint within 30 days and we credit the full €3,500 fee.
(06)
the audit scopes the work
The audit identifies bottlenecks; the roadmap scopes their fixes.
We trace bottlenecks across the browser, edge, and backend. The roadmap estimates cost and effort, then recommends a migration sprint, fractional systems pod, or keeping the current platform.
[01]
the audit
Five days, €3,500. The audit identifies what slows the platform and estimates the cost of each bottleneck.
[02]
scope the work
On day five, we scope a migration sprint for structural changes or a pod for ongoing engineering.
[03]
implementation
The same principal engineers implement the agreed fixes on your infrastructure and monitor them in production.
(07)
questions
Questions about the audit and next steps.
(01) What do I get at the end?
A CrUX-segmented Core Web Vitals diagnostic, a hydration and bundle map, a server-side trace report, and a prioritized, PR-ready remediation roadmap with effort estimates. You keep all of it whether or not you work with us after.
(02) Why does the whole fee roll into the work?
If you sign a migration sprint within 30 days, we credit the full €3,500 audit fee. You keep the roadmap either way.
(03) Do you implement the fixes?
Yes — the same principals who found the bottleneck remove it. Structural bottlenecks move to a fixed-scope migration sprint; ongoing performance and Core Web Vitals work runs on the fractional systems pod, on your infrastructure and watched by continuous monitoring.
(04) What if the bottleneck turns out to be the backend?
The audit includes server traces for API waterfalls and cold starts. The roadmap scopes any backend work.
(05) What access do you need?
Chrome User Experience Report access for your domain, read access to the repo, and your hosting or edge dashboard for cache and TTFB data. No production write access until you approve the work.
start with the audit.
The five-day audit identifies what slows the platform and estimates the cost of each bottleneck. Sign a migration sprint within 30 days and we credit the full fee.