Audit
$299
Detailed performance report with fix list
- Full Core Web Vitals audit
- PageSpeed Insights analysis
- Image optimization review
- JS/CSS bottleneck report
- Prioritized fix roadmap
- Delivered in 3 days
Performance
Core Web Vitals audits with before-and-after numbers
LCP, INP and CLS diagnosed against real field data rather than a lab score, then fixed, and measured again so you can see what moved.
What you get
Targeted performance audits and fixes delivering 25–35% average speed improvements. Your site passes Core Web Vitals and loads in under 2 seconds.
- core web vitals audit
- core web vitals consultant
- improve lcp
- fix inp
- website performance audit
Scope and pricing
Audit + Fix
$799
Audit plus hands-on implementation
- Everything in Audit
- Image compression & WebP
- Lazy loading setup
- CSS/JS optimization
- Caching configuration
- CDN setup
- Before/after report
Ongoing
$299/mo
Monthly monitoring and maintenance
- Monthly performance report
- Proactive fixes included
- Core Web Vitals monitoring
- Security updates
- Priority response
These are fixed prices for a defined scope, not hourly rates or starting points. Anything outside the scope gets quoted before it starts, never added to an invoice afterwards.
Questions we get asked
My Lighthouse score is green but Search Console says I am failing. Why?
Lighthouse is a lab run on a simulated device; Search Console reports CrUX field data from real visitors on real networks. Field INP in particular is usually worse than lab, because lab never clicks anything. I audit against field data for exactly this reason.
What does the audit actually deliver?
A prioritised list of what is costing you milliseconds, with the evidence for each item and an estimate of the gain. Not a Lighthouse screenshot with generic advice attached. You can hand it to your own team or have me implement it.
How much improvement is realistic?
Across 20+ audits the average LCP improvement has been about 28%. One WooCommerce rebuild went from 6.0s to 1.8s. But the honest answer depends on the cause. A render-blocking third-party tag is a fast win, a fundamentally heavy page is not.
Do you fix it, or just report it?
Either. Some clients want the diagnosis and have the engineering capacity to act on it; others want it handled. The audit is priced separately from the implementation so you are not committed to both.
Write-ups from this work
Problems we hit on real projects and wrote down. The clearest evidence that this is a lane we actually work in.
Start here
Tell me the problem and I will tell you whether we are the right studio for it. If we are not, I will say so rather than quote you anyway.