A handmade business with a performance problem
Corset Carriage is a one-person handmade fashion business run by Melissa, who designs and sews every corset and costume piece herself. Her work is meticulous and her customer base is loyal — but her website was quietly undermining both. On mobile, the site took nearly 20 seconds to load. For customers browsing between Pinterest tabs and Etsy storefronts, that wait meant lost sales before a single product was ever seen.
What a 39 PageSpeed score actually means
PageSpeed Insight scores are not abstract grades. A score of 39 means real customers on real phones are staring at a blank or partially-rendered screen. For Corset Carriage, the Largest Contentful Paint — the moment the main product image becomes visible — was clocking in at 18.3 seconds. The Speed Index was 10.9 seconds. The Cumulative Layout Shift was 0.499, meaning buttons and images were jumping around as the page loaded, causing accidental taps and abandoned sessions. This was not a minor inconvenience — it was the digital equivalent of a locked front door.
Going headless: what it is and why it matters
The root cause was architectural. WordPress on shared hosting is not built for the kind of performance a modern product business needs. Every page load triggered dozens of PHP processes, plugin calls, and database queries on a server shared with hundreds of other sites. The fix was not a faster theme or a caching plugin — it was a platform change. We rebuilt the Corset Carriage frontend as a headless Next.js 14 application. WooCommerce stays in the picture, but only as an API: it handles product data, inventory, and orders behind the scenes while the customer-facing site is a completely separate, statically-generated Next.js app deployed to Vercel's global edge network.
The numbers after the rebuild
The results were not incremental. Mobile Performance Score: 39 → 100. Largest Contentful Paint: 18.3 seconds → 1.8 seconds — a 10× improvement. Speed Index: 10.9 seconds → 1.4 seconds. Cumulative Layout Shift: 0.499 (failing) → 0 (perfect). These are not rounded estimates — they are Lighthouse scores captured against the rebuilt site running on Vercel. The site now loads faster than 99% of ecommerce sites globally, a benchmark that matters both for conversion and for AI search visibility.
Technical stack
The production stack is straightforward by design: Next.js 14 with the App Router for the frontend, WooCommerce REST API for product and order data, Vercel for deployment and edge delivery, and static site generation for product pages so every page is pre-built at deploy time rather than rendered on demand. There are no WordPress plugins in the critical path. There is no shared hosting. The result is a site that behaves like a native app — instant transitions, zero layout shift, and consistent performance regardless of server load.
What this means for your business
Corset Carriage is pre-launch — the DNS cutover to the new site is pending Melissa's go-ahead. But the performance data is already captured and confirmed. If your site was built on WordPress shared hosting and you sell products or services online, the Corset Carriage numbers are a reasonable proxy for what a rebuild could do for you. The gap between a slow site and a fast one is not cosmetic. It is customers who leave before they ever see your work — and AI search engines that skip your site entirely because they can't parse it fast enough. Start with a free snapshot and we'll show you exactly where you stand.
Ready to see what's possible for your business?