Gourmet Furnishers

The previous site ran on WordPress with Elementor and WooCommerce handling content and commerce in a single, tightly coupled stack. That combination scales fine for a small catalog with modest traffic. It does not scale for a brand pulling thousands of visitors a month across three distinct product lines — furniture, KDW (kitchens, doors, wardrobes), and Gourmet Homes. Every page render meant PHP assembling Elementor's widget tree, WooCommerce querying the catalog, and a browser downloading whatever CSS and JS those plugins decided to ship, on every single visit. The result was a heavy initial load with a large number of requests before a single product image appeared. The team's answer at the time was a preloader — a sequence of brand and product imagery shown while the page assembled itself behind it. It was a reasonable instinct: if people are going to wait regardless, use the wait to introduce the brand. But it was solving the wrong problem. It hid the slowness instead of removing it, and it put the one place explaining what Gourmet Furnishers actually is — a furniture brand with a Homes division and a KDW division living inside it — directly in the path people were most motivated to get past. Hotjar recordings confirmed it: visitors landed, sat through the preloader, skimmed two or three homepage sections, and went straight into categories. The introduction nobody could skip was also the introduction nobody was watching.

The fix was not a faster preloader or a shorter intro. It was removing the reason a preloader existed at all. The rebuild decouples the site into two systems. WordPress and WooCommerce, moved onto a locked-down subdomain, keep doing what they were already good at — product catalog, order management, and content tools the team already knew. Next.js, running on the primary domain, became the only thing a shopper's browser has to render. It talks to WordPress and WooCommerce purely through their REST APIs, fetching only the data a page needs rather than shipping a page builder's worth of markup and scripts. Product and content updates in WordPress now trigger the frontend's revalidation endpoint directly, so publishing a product does not require a full rebuild — pages regenerate on demand and stay cached until something actually changes. For a catalog running close to 300 products across three verticals, that is the difference between every content edit costing a deploy and costing nothing.

With the heavy backend fixed, the preloader had nothing left to hide, so it came out entirely. The homepage now renders on arrival. The brand story that used to run before the site — Gourmet Furnishers, Gourmet Homes, and the KDW line, three distinct offerings people consistently misread as one — moved into a scroll-driven reveal on the homepage itself instead of a gate in front of it. Nobody has to sit through an introduction to see it; it now surfaces to people already moving through the page on their way to browse, which is the behavior Hotjar showed was happening regardless. It is the same information, delivered to someone already in motion instead of someone waiting for permission to move.

The visual language shifted alongside the architecture. The new design leans into a dark, editorial hero built around Playfair Display headlines over full-bleed lifestyle photography, with the Gourmet orange as the one consistent accent against a near-black or white ground depending on section. The header now does real work: a mega-menu split cleanly across Furniture, KDW, and Homes, with the Gourmet Homes sub-mark treated as its own visual identity nested inside the parent brand rather than folded into one generic products menu.

Beyond the homepage, the UX work focused on things Elementor made expensive to build well. A Curated Package Creator lets a shopper assemble a room from individual pieces and automatically applies a 30% bundle discount at checkout. A multi-step Lead Wizard handles bespoke consultations — Kitchens, Wardrobes, Doors, or full Homes projects — writing straight to custom WordPress tables instead of a generic contact form. City-based landing pages handle localized search intent without duplicating page templates by hand.

Motion is handled by GSAP paired with Lenis for smooth scroll, driving the scroll-triggered reveals that now carry the brand introduction. Nothing here blocks interaction the way the preloader did — every animation runs against a page that has already loaded, so it is additive rather than a gate.

The stack is Next.js 16 on the App Router with React 19, talking to a headless WordPress and WooCommerce backend isolated on its own subdomain and CORS-locked to the production domain. Checkout, orders, contact forms, and newsletter signups run through server-side API routes rather than exposing WooCommerce credentials to the client, with Zod validating input and Cloudflare Turnstile guarding public forms against bots. A dedicated revalidation endpoint, triggered from WordPress on publish, keeps pages fresh without a full redeploy — necessary at close to 300 SKUs across three verticals. The frontend runs as a separate Node.js web app from the WordPress instance it depends on.

Migrating a site with an established search footprint to an entirely different architecture carries real risk, so preserving existing rankings was a hard constraint, not a nice-to-have. Structured data is generated per page type, sitemap and robots output are built dynamically rather than hand-maintained, and a custom SEO registry keeps per-page metadata synced from WordPress into the Next.js frontend, so editors keep controlling SEO fields from an interface they already know without needing a deploy to change a title tag.

The hardest part was not the frontend, it was making the migration invisible to WooCommerce's existing workflows and to search engines at the same time. Checkout, cart, and order logic had to be rebuilt against WooCommerce's REST API instead of its native PHP checkout flow, without changing how orders show up for the team already running the business through it. Custom features like the package bundler and lead wizard had no page-builder plugin to lean on this time; both were built from scratch to replace functionality Elementor plugins used to provide out of the box.

The rebuild moved the frontend to Next.js while WooCommerce and WordPress kept running the business underneath — catalog, orders, and content never stopped during the transition. WordPress and WooCommerce were relocated to an isolated, CORS-restricted subdomain first, before the Next.js app took over the primary domain.

The clearest number is load time: the new headless build is more than 50% faster than the Elementor and WooCommerce site it replaced, on a domain carrying thousands of monthly visitors — the exact traffic volume that made the old architecture's overhead expensive in the first place. Removing the preloader means every visitor now reaches the homepage instantly instead of waiting through an intro engineered to be skipped, and the brand story that intro was supposed to carry now sits inside the path people were already taking through the site.