Hands-on feedback: why Next.js became my go-to foundation for my clients' showcase sites, online booking systems and shops.
A craftsman's choice, not a trend
When a client entrusts me with their website, I commit to three things: it has to be fast, it has to rank well, and it has to evolve without needing a full rebuild two years down the line. After delivering very different projects — a podiatrist's practice, a sophrologist's booking area, the site of an events brand, and the one you're reading right now — Next.js naturally established itself as my default foundation. Not because it's fashionable, but because it's the only tool that keeps all three of those promises at once without piling on unnecessary complexity.
A concrete example: a sophrologist's booking system
For a sophrologist's website, the real need wasn't a brochure: it was letting her clients book a session at 10pm from their sofa, and letting her block out her holidays without calling me. With Next.js, the presentation pages are generated ahead of time and load instantly, while the booking module queries the database in real time to show available slots. That blend of ultra-fast static content and dynamic behaviour exactly where it's needed is what the framework does best — and it's very hard to achieve cleanly with a traditional WordPress site.
Performance is not optional
Google measures your site's speed (the famous Core Web Vitals) and factors it into your ranking. Your visitors don't measure anything: they simply leave if the page takes more than three seconds to appear. Next.js optimises the heavy stuff out of the box: images are served in modern formats at the exact size of the screen, the code is split so only what's needed gets loaded, and critical pages are pre-built. On my projects, I systematically aim for a PageSpeed score above 90 on mobile — and I check it on the live production site, not on my own machine.
Five languages without the overhead
The Elaphe Studio website exists in French, English, Spanish, Portuguese and Vietnamese. Each visitor is directed to their language based on their country and browser preferences, and every page properly tells Google about its translated versions through hreflang tags. This kind of multilingual architecture, which often blows up budgets, comes together very naturally with Next.js: the language is part of the page's address, the content comes from the database, and everything else follows. For a client targeting an international audience, that's a genuine competitive advantage.
Client autonomy, built in from day one
All my sites ship with an admin dashboard: clients update their own text, photos, prices and availability, with no editing fees and no dependence on me. Technically, it's the same Next.js application serving both the public site and the admin area, connected to the same database. One project to maintain, one hosting bill, no fragile synchronisation between two systems — and a client who's self-sufficient from the very first week.
When I don't choose Next.js
A bit of honesty: Next.js is not the answer to everything. If you already have a well-maintained WordPress site that does its job, migrating it on principle would be money wasted. And for a simple event page that will live for three months, a lighter tool is more than enough. My job is to pick the right tool for your situation — not to sell everyone the same hammer. But as soon as a project needs to last, evolve and perform, Next.js is what I recommend, because it's what I'd use for myself. The proof: this site runs on it.
What it changes for you
A site built on modern foundations is a site that loads fast everywhere, that Google understands well, and that will happily accept the feature you haven't thought of yet two years from now — a client area, a payment module, an AI assistant. If you want to see what that would look like for your business, the online estimator gives you a price range in two minutes, and I personally reply to every enquiry.