React / Next.js
React & Next.js builds that load fast and rank
Most React sites are slow because they render in the browser and ship metadata the crawler never sees. I build with the App Router, server components and real metadata — so the page is fast for people and legible to search engines.
What you get
The parts of the job that decide whether it works.
Server-first rendering
App Router with server components by default. Client JavaScript only where interaction genuinely needs it.
Metadata that ships
Per-route titles, descriptions, canonicals, Open Graph and JSON-LD generated on the server — not injected after hydration.
Core Web Vitals
Prioritised LCP images with correct sizes, no layout shift, and route-level code splitting.
Accessible components
Keyboard-navigable, visible focus, correct landmarks and heading order. Tested, not assumed.
Design systems
Tailwind tokens and a component library your team can extend without re-litigating spacing every sprint.
Any backend
Headless CMS, REST, GraphQL or your existing API. Typed data access and sensible caching.
How it works
Four stages, no surprises about what happens when.
- 1
Scope & architecture
Route map, rendering strategy per page, and a decision on what genuinely needs to be a client component.
- 2
Design system
Tokens, base components and layout primitives so every subsequent page is assembly, not invention.
- 3
Build
Pages built server-first, with metadata and structured data written alongside the markup rather than bolted on.
- 4
Measure & hand over
Lighthouse and field data checked on real devices, analytics wired, and documentation your team can act on.
What ships
Everything below is included, not quoted as an extra later.
- Next.js App Router codebase
- Reusable component library
- Per-route metadata & JSON-LD
- Sitemap, robots and canonical strategy
- GA4 or your analytics of choice
- Deployment pipeline & preview environments
- Accessibility pass (keyboard, contrast, landmarks)
- Handover documentation
Questions people actually ask
Next.js or plain React?
If the page needs to rank, Next.js. Client-only React sends an empty shell to the crawler and pays for hydration before anything is visible. For an internal dashboard behind a login, plain React is fine.
Can you work with our existing codebase?
Yes. I most often come in to fix rendering strategy, metadata and Core Web Vitals on a build that already exists, rather than starting over.
How long does a typical build take?
A marketing site with 8-12 routes is usually 3-5 weeks. Complex applications depend on how settled the requirements are.
Do you handle hosting?
I set up deployment on Vercel or your preferred platform, including preview deployments per branch. Ongoing hosting stays in your account, in your name.
What it costs
Three starting points — Launch, Growth and Scale — with the scope tailored in discovery. The full breakdown sits on the services page.
See pricingReady to talk about react / next.js development?
Tell me where you are now and what you are aiming for. You will get a straight answer on scope, timeline and whether I am the right person for it.