What we learned rebuilding the largest Nordic electronic retail website in Next.js?
summary
Rebuilt the Elkjøp/Elgiganten/Gigantti frontend in Next.js and deployed on Vercel, going from a slow Angular site to a production rollout in under a year and 100% traffic on the new app. Proof of concept uses three developers instead of the prior ~20 and shows Core Web Vitals in the green with mobile scores near 99 and page loads dropping from minutes to seconds. Key decisions: ditch edge runtime for Vercel Functions, use Next.js app router and React Server Components, edge-configged LaunchDarkly flags plus middleware for i18n, explicit caching and streaming partial rendering.
AI-written summary · about
chapters (17)
- 0:00Next.js rebuild journey
- 1:53Slow site impact on revenue
- 4:26Thomas Jansson at Lar Nordic
- 5:30Organizational change for rewrite
- 10:37Business case for Next.js
- 13:05Why Next.js over others
- 17:25Proof of concept to production
- 19:52Network jumps and CDN costs
- 21:35Next.js app router benefits
- 25:26React server components
- 28:55Internationalization with middleware
- 31:47Feature toggling with LaunchDarkly
- 35:41Server actions in practice
- 39:17Next.js caching strategies
- 43:13Part rendering and streaming
- 48:36Vercel features for dev
- 52:51Summary and lessons learned
related talks
01h 01mLearnings from One Year in Production with Next.js on Vercel
22mOptimization strategies for a performant, headless storefront
33mVercel + Vue.js
45mNext js: Build a State of the Art E commerce in Fullstack React
32mBuilding the world's largest grocery site in React
25mBuilding the Fastest Commerce Site: How we Built Next js Commerce 2 0
39mNavigating front-end architecture like a Neopian
17mThe Frontend Cloud: Crafting superior web experiences