Next.js developer
I use Next.js knowing how it actually works, not by copying a starter: the server/client component boundary, choosing a render strategy (SSG, ISR or SSR), caching behaviour and bundle size. Those details decide how fast the finished site really is.
What's included
- Greenfield builds with the Next.js App Router
- Joining an existing codebase, or migrating Pages Router to App Router
- Render strategy selection: static, ISR or server-side
- Core Web Vitals optimisation (LCP, CLS, INP)
- Structured data and technical SEO
- Type safety with TypeScript
- Vercel deployment, environment and domain configuration
How it works
- 01
Audit
If a project already exists, we start with a performance and architecture audit — you get a written list of issues.
- 02
Plan
We prioritise changes by what each one will actually gain you.
- 03
Execution
Applied step by step, with a measurable result at each stage.
- 04
Measurement
Before and after numbers: load time, Lighthouse score, bundle size.
Frequently asked questions
- My existing site is slow — can you help?
- Yes. We start with an audit to find the actual cause (images, bundle size, render strategy, third-party scripts) and I give you a prioritised fix plan. A handful of targeted changes usually makes a large difference.
- Can you join our team temporarily?
- Yes — hourly or project-based engagement with an existing team works fine.