The technology behind your website: why I build on Next.js

When a client asks me “what are you going to build my site with?”, they rarely expect a technical answer. And that’s fair: what matters to them is that the site is fast, that it shows up in Google, and that it won’t break on a Friday night. Those three things are decided precisely by the technology choice.

Fast by design, not by accident

Most slow sites are slow because they ship the browser a mountain of code to run before anything appears. Next.js does the opposite: pages are rendered ahead of time, on the server, and arrive ready to read. The visitor sees the content immediately; everything else wakes up in the background.

In practice that means sub-second load times, even on a phone in a basement. And Google measures exactly that.

SEO taken seriously from day one

A well-built site hands Google clean, structured, already-rendered content — not an empty shell a crawler has to guess at. Next.js lets me generate, for every page:

• clear, readable URLs (/blog/my-article instead of a cryptic id);
• unique title and description tags, in French and English;
• structured data (Schema.org) that helps Google understand the page;
• a sitemap and hreflang tags generated automatically.

Bilingual, no compromise

In Québec, a serious site lives in French first, often in English too. Rather than duplicating two sites, I run both languages from a single codebase: same features, same performance, translated URLs (/realisations and /work). One thing to maintain, two audiences well served.

The right technology is the one you never notice: the site is simply fast, findable and built to last.

You don’t need to understand React to benefit from it — that part is my job. But if you’re wondering why your current site drags its feet, the answer is often right there, under the hood.