Productized · Fixed scope · 10 business days

Core Web Vitals Audit

Your LCP is over 2.5s. Your INP keeps regressing after each release. CLS jumps when an ad slot loads. You don't need another tool. You need someone to read the trace and ship the patches. That's this engagement.

Request an audit
Read my LCP playbook

What you get

A written audit, a prioritized fix list, and the patches that move the numbers most. Fixed scope, fixed fee, fixed timeline. No retainer pressure.

  • Real-user metrics diagnosis

    Field data from CrUX, your RUM provider (Vercel Speed Insights, SpeedCurve, Sentry), or a temporary collector if you don't have one. LCP, INP, CLS broken down by route, device, and country.

  • Lab profiling

    Lighthouse, WebPageTest, and Chrome DevTools traces of the worst offenders. Render-blocking resources, third-party costs, hydration timing, layout shifts.

  • Written report

    10–20 pages, every finding with evidence (screenshot, trace, metric), prioritized by impact-to-effort ratio. The report stands on its own; your team can ship from it without me.

  • High-impact patches

    Pull requests for the top three findings. You merge them and watch the numbers move before the engagement ends.

How the 10 days go

  1. Days 1–3 · Data. RUM access, repo access, production URLs. I collect field data and run lab profiles on the worst-performing routes.
  2. Days 4–6 · Diagnosis. Trace the actual cost, not the obvious suspects. Hydration, JavaScript execution, font and image strategy, third-party scripts, server response time.
  3. Days 7–8 · Patches. Pull requests for the highest- impact fixes. Reviewed against the team's existing standards.
  4. Days 9–10 · Report & handoff. Written report, walkthrough call, plan for the work I'm not shipping. You leave with a roadmap, not just a diagnosis.

What this audit will not do

Productized means scope is fixed. Things outside the scope are honest questions. Happy to handle them in a separate engagement, but not in this one.

  • Full rebuild of a slow application (that's a build engagement)
  • SEO audit beyond Core Web Vitals (that's a different service)
  • Backend performance tuning. I'll point at it but won't fix database queries or API latency
  • Native mobile performance (iOS/Android profiling)

Who this is for

  • Next.js teams failing Core Web Vitals on the page type that drives revenue (PDP, signup, landing).
  • React SPAs with bundle bloat, slow time-to- interactive, or hydration cliffs after framework upgrades.
  • Engineering leaders who need an outside opinion to unblock a stalled internal performance project.
  • Marketing teams losing ranking and conversion because the engineering backlog can't prioritize the work.

Frequently asked

How long does a Core Web Vitals audit take?
Ten business days from kickoff to written report. The first three days are data collection from real-user metrics and lab profiling; the rest is targeted diagnosis, prioritized fixes, and a written plan.
What stacks do you audit?
Next.js (App Router and Pages), React (Vite, Remix, CRA), Astro, and Gatsby. Server-rendered, static, and SPA architectures. If you can give me a production URL and repo access, I can audit it.
Do you fix the issues or just report them?
Both are options. The standard audit ships the plan and the highest-impact patches. If you want the full remediation shipped end-to-end, we move into a build engagement after the audit.
Will this help my Google rankings?
Core Web Vitals are a ranking signal for Google Search, but they are not the dominant signal. The honest answer: fixing CWV won't 10x your traffic on its own, but it will lift pages that are already close to ranking and improve conversion across the board.