Core Web Vitals audits
Measure first with Lighthouse and real-user data where you have it, so effort goes to what hurts users, not to what's easy to change.
Performance · Part-time engagements
React and Next.js performance engineering
Improving FCP, LCP and Core Web Vitals on high-traffic consumer pages is a core part of my role as Technical Lead at Myntra. I take on a small number of part-time engagements to find out why your React or Next.js app is slow and fix the parts that matter.
What I build
Rendering and loading strategy
What should be server-rendered, static, revalidated or lazy-loaded, and when. Often the biggest win and a cheap one.
Bundle and image work
Bundle analysis, code splitting, lazy loading and image optimisation. Most slow pages are shipping more JavaScript and bigger images than they need.
Frontend architecture that stays fast
Patterns and guardrails so performance doesn't regress the next time someone adds a feature.
When you should hire me
- Your Lighthouse or Search Console Core Web Vitals report is red and you don't know where to start.
- A key page, such as a product page, landing page or listing, loads noticeably slowly.
- Your bundle has grown over time and nobody owns it.
- You're about to invest in SEO and want the performance foundation right first.
How an engagement runs
Measure
Baseline the pages that matter, on realistic devices and networks.
Diagnose
Find the actual bottlenecks: render path, bundle, images, third-party scripts, layout shifts.
Fix the highest-impact items
Implement the changes with your team, or hand over a prioritised list if you'd rather do it in-house.
Re-measure
Confirm the numbers moved, and leave guardrails behind.
Relevant experience
Myntra: Mnow
Implemented lazy loading on product racks for the hyperlocal 2-hour delivery product, resolving SLA discrepancies and improving FCP/LCP.
Myntra: consumer surfaces
Drove FCP, LCP and Core Web Vitals improvements across Myntra's consumer surfaces.
Technomanagers.in
Core Web Vitals work as part of a migration from Lovable to Next.js, alongside the SEO overhaul.
Selected projects
The full write-ups, including what I decided and why.
Client work · Next.js migration & SEO
Technomanagers: Lovable to Next.js migration
A client site for Technomanagers, originally built with Lovable, migrated to Next.js with an SEO overhaul.
Read the case studyTechnologies
- React
- Next.js
- Lighthouse
- Core Web Vitals
- Bundle analysis
- Lazy loading
- Image optimisation
- ISR / SSR
FAQ
Do you take full-time roles?
No. I work full-time as a Technical Lead at Myntra and take on a small number of part-time freelance and contract engagements alongside that.
Can you guarantee a Lighthouse score?
No, and be wary of anyone who does. Scores depend on your content, third-party scripts and devices. I can promise to measure properly, fix the biggest causes first and show you the before and after.
Do you only work on Next.js?
No. I work on React apps generally, including client-rendered ones, and on React Native performance.
Can you work with my team rather than alone?
Yes. I'm used to leading a team. I can pair with your engineers, or hand over a prioritised plan.
Can you work remotely with international teams?
Yes. I'm based in Bengaluru, India, and available for remote part-time engagements worldwide.
Need senior engineering capacity without hiring another full-time engineer?
Tell me what you're building and what you need help with. I'll reply with an honest take on fit and scope.
Start a projectPart-time freelance and contract engagements · Remote, worldwide