Next.js web development in Kathmandu

Server first, animation second

The default in a Next.js App Router project should be a server component. Content arrives as HTML, which means it is visible before any JavaScript runs and it is present when a crawler reads the page. Interactivity is added where it is actually needed: a filter, a form, a canvas.

That order matters for a portfolio or a marketing site because the visitor usually wants exactly one thing from the page. If the answer to their question is inside a client bundle that arrives after three seconds, the design is decoration around a delay.

Technical SEO is part of the build, not a plugin

Canonical URLs, one H1 per page, generated sitemaps, structured data as a connected graph and redirects that resolve in a single permanent hop. All of that is code in the repository, checked by a script that fails the build when a title runs past 60 characters or a description leaves the 140 to 155 band.

The reason for the strictness is that these rules decay quietly. Someone edits a page in a hurry, a title doubles, and nobody notices for six months. A build-time check is the only version of a content rule that survives contact with a team.

Performance as a budget, not an audit

LCP under 2.5 seconds, CLS under 0.1 and INP under 200ms are targets agreed before the first commit, because retrofitting performance into a finished design costs three times as much. In practice that means reserving space for anything that loads late, keeping the largest element as text, and loading 3D or heavy animation libraries only where they are used, behind a dynamic import.

I report the numbers per route at handover, including the page weight, so the client can see what changed rather than taking a claim on trust.

How the process runs

1. 01Content model first: what each page type has to carry, before any layout
2. 02Design system: tokens, primitives and layout rules reused across page types
3. 03Build with the SEO layer wired into the templates rather than added per page
4. 04Performance pass per route, with the numbers written down
5. 05Launch, then verify redirects, sitemap, canonicals and structured data on the live host

How pricing works

Fixed price per site once the page types are known, because a marketing site with five page types is a different job from one with fifteen. For ongoing products I work in weekly blocks with a demo at the end of each. Discovery is short and free, and the estimate follows it.

Questions about next.js websites