Field data analysis
CrUX or your own RUM. The metrics Google uses, broken down by page type and device.
// performance audit
Performance audit, prioritized fixes.
Audit work for teams whose pages are losing rankings to faster competitors. We measure with real-user data, write down what's slow and why, and prioritize the fixes by impact.
// where teams get stuck
Your Lighthouse score is 90. Your INP is 700ms.
- Lab metrics that don't match what users feel.
- INP regressions that landed three deploys ago and nobody noticed.
- Image optimization "done" but LCP still drags.
- JavaScript budget that grew 2× while features grew 1×.
// what's included
What you get.
Lab profiling
DevTools traces, flame graphs, network waterfalls. The why behind the numbers.
Prioritized fix list
Each fix scored by impact and effort. The first three move the needle; the rest are housekeeping.
Written report
PDF you can hand to your team. Findings, recommendations, code-level examples.
Optional pair-fix sprint
We work alongside your team to ship the top fixes, if the scope includes it.
// how we work
Three phases. Compressed.
01 · Calibrate
Access setup, baseline measurements. Written scope.
02 · Audit
Field + lab data. Findings doc circulated mid-week.
03 · Deliver
Final report. Walkthrough call. Optional pair-fix block.
// common questions
What teams ask before signing.
LCP, INP, CLS, TTFB. INP is the one most teams haven't tuned for since it replaced FID.
The audit deliverable is the report. The pair-fix sprint is optional, scoped separately.
A focused window for the audit, then an optional pair-fix sprint sized to findings. We share the timeline in the written proposal after the discovery call.
Scoped per audit. Pair-fix billed separately by scope. We send a written proposal after the discovery call.
Murcia, Spain.