From slow to 95+ Lighthouse — with a written plan and real results
Core Web Vitals fixed, bundle sizes cut, LCP under 2.5 seconds. I audit, prioritize, and implement — or give you the plan to do it yourself.
A slow site doesn't just frustrate users — it costs you ranking positions and conversion rate. Studies consistently show a 100ms increase in page load time drops conversions by 1%. I've taken sites from 38 → 97 Lighthouse and know the exact sequence: measure on real users, find the 20% of fixes that unlock 80% of the score, and implement without regressions.
38→97
Best single-project Lighthouse improvement
2×
Organic traffic uplift documented after CWV fixes
<2.5s
LCP target on every delivered project
0.1
CLS or below on all delivered pages
Trusted by founders & teams in
Everything included in every engagement
No upsells. No surprise change orders. One scope, one price.
Performance audit report
Full analysis with Lighthouse, WebPageTest, and Chrome UX Report (real-user CrUX data). Every issue severity-ranked by impact on LCP, CLS, INP, and TTFB — with implementation instructions.
LCP under 2.5 seconds
Largest Contentful Paint fixed via image optimization (next/image, AVIF/WebP, preload hints), critical CSS inlining, server response time improvements, and removing render-blocking resources.
Bundle size reduction
Webpack Bundle Analyzer or Rollup Visualizer teardown. Tree-shaking dead imports, code-splitting by route, replacing heavy libraries, and lazy-loading below-fold components.
CLS elimination
Every layout shift tracked to its source: unsized images, late-loading fonts, injected banners, dynamic content without reserved space. Fixed to 0.1 or below.
Server response time (TTFB)
Database query profiling, N+1 query fixes, Redis caching for hot paths, edge CDN configuration, and API route response-time instrumentation.
Before/after evidence
Lighthouse comparison, WebPageTest filmstrip, and a CrUX dashboard showing real-user improvement over 28 days. Stakeholder-ready results you can share.
The tools I actually use in production
Modern, battle-tested, and chosen for fit — not hype.
Measurement
- Lighthouse CI
- WebPageTest
- Chrome UX Report
- Datadog RUM
Frontend
- next/image
- next/font
- Bundle Analyzer
- Preload / Prefetch
Backend
- Redis
- Prisma query logs
- pg_stat_statements
- EXPLAIN ANALYZE
CDN & Infra
- Vercel Edge
- Cloudflare
- AWS CloudFront
- Cache-Control headers
How we'll work together
Predictable, written-down, no surprises.
- 01
Baseline measurement
Lighthouse + WebPageTest + CrUX field data. I measure on real mobile hardware, not just desktop. No fixing what we haven't measured.
- 02
Prioritised fix plan
Each issue gets an effort vs impact score. The top 5 fixes typically unlock 80% of the score gain. We agree on what's in scope before work starts.
- 03
Implementation
Fixes shipped in small PRs with before/after Lighthouse diffs. No regressions — Lighthouse CI gates every PR.
- 04
Evidence report
Final Lighthouse comparison, WebPageTest filmstrip, and 28-day CrUX trend. A document you can use to show stakeholders what changed and why.
Pricing that matches the work
Starting prices. Final quote in writing after a 30-minute scoping call.
Audit only
Get the plan, implement yourself
$500starting
- Full Lighthouse + WebPageTest + CrUX analysis
- Severity-ranked issue list with fix instructions
- 30-min walkthrough call
- Delivered in 3 business days
Audit + Implementation
Full fix on a live production site
$2,500starting
- Full audit as above
- Top-priority fixes implemented
- Lighthouse CI added to your pipeline
- Before/after evidence report
Ongoing monitoring
Prevent regressions as you ship
$800/mostarting
- Monthly Lighthouse + CrUX review
- Regression alerts + fix PRs
- Quarterly full audit
- Cancel any time
Questions I get asked first
Our Lighthouse score is good in the tool, but real users report it's slow. Why?+
Lighthouse desktop emulates a fast CPU and fast network. Real users on mobile 4G see different results. I always measure with CrUX (28-day real-user data) and WebPageTest on a throttled mobile connection. The lab score and field score often diverge significantly — field data is what actually affects your Search ranking.
Will improving performance affect our SEO?+
Yes, directly. Core Web Vitals are a confirmed Google ranking signal. Improving LCP, CLS, and INP to 'Good' thresholds on the CrUX field data removes a ranking suppressor. The effect is usually visible in Search Console within 4–6 weeks.
Can you optimize a WordPress / PHP site, or only React/Next.js?+
Primarily React, Next.js, and Node.js stacks. For WordPress I can advise on caching strategy, image delivery, and CDN configuration, but I won't implement PHP-level changes.
How long do the improvements last?+
Performance regresses when new code ships without measurement gates. As part of the engagement I add Lighthouse CI to your pipeline so every PR shows a Lighthouse delta — regressions get caught before they reach production.
Let's scope your project
Tell me what you're building. I'll reply with a written estimate within 24 hours — no sales call required.
Related services
Often paired with performance optimization.
Web Development
From the database schema to the deployed Next.js frontend, I ship modern web apps designed to rank, convert, and scale. One engineer, full ownership.
Next.js Development
App Router, React Server Components, TypeScript strict, Tailwind, and a 95+ Lighthouse score on real data. Frontend-only or full-stack — I'll fit your team.
Technical SEO
Core Web Vitals, schema, indexation, and JavaScript-rendering work — by someone who reads the Next.js source, not just the SEO tool report.
Frontend Development
Production-grade React and Next.js frontends with a focus on accessibility, performance, and design systems. Built to scale across teams and devices.