Simple buying decisions.
Clear boundaries.
The goal is to make the engagement easy to understand while protecting the codebase, timeline, and scope.
01Do you guarantee a Lighthouse 90+ score?
No. I do not sell cosmetic Lighthouse scores, and a Lighthouse 100 is never promised. I focus on Core Web Vitals, main-thread blocking, rendering cost, mobile responsiveness, bundle weight, and user-perceived performance, then validate before and after under comparable conditions.
02My app was built with AI tools (Cursor, v0, Copilot). Can you help?
Yes. I review and improve React/Next.js frontends built or accelerated with Lovable, Replit, v0, Cursor, Copilot, or similar tools when they need production hardening, such as client-side bloat, duplicate logic, or weak loading states.
03Which tier should I choose?
Choose the smallest tier that answers your next decision. Start with Performance Triage Lite when the cause is unclear (one page). Choose Prod Readiness Diagnostic for a deeper audit and roadmap across up to 5 pages. Choose Performance Recovery Sprint when you already know the problem and want the highest-impact fixes implemented and validated across up to 7 pages.
04Will optimization break my existing functionality?
That is what the process is built to prevent. Each proposed change connects to a measured bottleneck, only agreed changes are implemented, and performance work has to coexist with your authentication, analytics, accessibility, and product needs. Results are re-tested under comparable conditions before delivery.
05What is not included?
Backend/database optimization, full redesign, new features, security audits, SEO content work, and complex WebGL/runtime architecture unless scoped separately. There is also no Lighthouse 100 guarantee. For example, on an order-management or POS dashboard I cover the agreed frontend flows only; payment, inventory, and order-routing backends are a separate scope.