Performance & Core Web Vitals Audit
A prioritised list of what is slowing your site down, with the numbers behind it.
A slow site loses customers silently. Nobody emails to say they left because the page took six seconds.
This is a fixed-scope audit of your live site: what is actually being downloaded, what is blocking the first paint, which images are shipped at the wrong size or format, and what your real Core Web Vitals are on a mid-range phone rather than on a developer's laptop.
You get a written report ranked by impact against effort, with the measured before-figures for each item so you can verify any fix. If you want the fixes implemented, that is quoted separately — but the report is yours either way, and it is written so another developer can act on it.
For reference, on a recent audit of a client site this process identified changes that took the main JavaScript bundle from 1,177.94 kB to 371.90 kB.
What you get
Bundle analysis
What is shipped, what is unused, what can be split.
Core Web Vitals on real hardware
LCP, INP and CLS measured on mid-range mobile.
Image and asset audit
Formats, dimensions, caching, compression.
Render-blocking analysis
What delays first paint and why.
Prioritised written report
Ranked by impact against effort, with measured baselines.
30-minute walkthrough call
So the report is understood, not just delivered.
Lighthouse · Chrome DevTools · WebPageTest · Bundle analysis
Questions about this
Do you fix the problems too?
The audit is the deliverable. Implementation is quoted separately once we both know the scope — which is fairer than quoting blind, and it means you are free to have your own team do the work.
What if my site is already fast?
Then the report will say so and point at what to watch as you grow. That is a legitimate outcome and you still get the baseline measurements.