NEXT.JS · PERFORMANCE · REMOTE
Make your Next.js app fast — measurably.
Core Web Vitals audits, App Router architecture reviews, RSC migration plans, and edge-runtime optimization. Independent, hands-on, remote.
·
By Amit Chakraborty — Kolkata, India · Remote worldwide
What you get
- Core Web Vitals audit — LCP, INP, CLS measured on real-user data (not just Lighthouse). I deliver a written report with prioritized fixes ranked by user impact.
- App Router + RSC migration — Pages → App Router migration plans that don't break SEO. Server Components where they help, Client Components where they have to be.
- Bundle surgery — Dynamic imports, route segment configs, package barrel-file removal. Typical wins: 30–60% smaller First Load JS.
- Edge runtime tuning — Move latency-sensitive routes to the edge. Cold-start optimization, ISR strategy, cache header design.
- SEO that survives the migration — Metadata API, structured data, canonical strategy, and sitemap generation that doesn't regress your existing rankings.
Proof
- Marketing site refactor · LCP 4.2s → 1.1s · INP 380ms → 90ms — Next 13 Pages → Next 14 App Router migration with RSC streaming and edge ISR.
- E-commerce product pages · First Load JS 410KB → 142KB — Bundle audit, dynamic imports, and a custom image pipeline replacing next/image for above-the-fold hero.
- Documentation portal · Lighthouse 62 → 99 · CLS 0.18 → 0.01 — Font loading strategy, layout-shift hunt, and route prefetch tuning.
How it works
- Day 1–3 — Audit — Real-user metrics from your Vercel Analytics or web-vitals.js, plus a synthetic Lighthouse run on every key route. Written report on Day 3.
- Week 1–2 — Quick wins — Fix the top 3 issues by user impact. Usually: image strategy, third-party script loading, font display.
- Week 3+ — Architecture — RSC migration, route segment config, edge runtime moves, ISR / cache strategy.
Frequently asked questions
How long does a Next.js performance audit take?
A focused audit takes 3–5 working days. I deliver a written report ranking issues by user impact, with code-level fixes for each. Implementation engagements run 2–6 weeks.
Do you work on Pages Router or only App Router?
Both. Many production apps are still on Pages Router or mid-migration. I'll meet your codebase where it is and recommend migration only when the ROI is clear.
Can you guarantee Lighthouse 100?
No serious engineer can guarantee a specific Lighthouse score on a real product. I can guarantee measurable improvement on real-user Core Web Vitals — that's what Google actually ranks on.