Site performance isn't an engineering metric in isolation — it's a conversion metric. A commerce site that loads in 1 second converts at a meaningfully higher rate than one that loads in 5 seconds. Search ranking is also affected: Google's Core Web Vitals are a ranking signal, and slow storefronts pay an SEO penalty that compounds over time.
BigCommerce Catalyst is a headless storefront framework built on Next.js that addresses both the performance and operational flexibility constraints of traditional theme-based storefronts — including BigCommerce's own Stencil framework.
What Catalyst Actually Is
Catalyst is BigCommerce's purpose-built headless frontend framework. It's not a theme — it's a React/Next.js application that connects to BigCommerce's backend through GraphQL APIs. The distinction matters:
- Stencil is a server-rendered, theme-based storefront tightly coupled to BigCommerce's backend. Customization is bounded by what the theme system allows.
- Catalyst is a decoupled application. The frontend is a separate codebase — built with React, rendered with Next.js, deployable to edge infrastructure — that communicates with BigCommerce through APIs.
This architecture enables what Stencil can't: full frontend flexibility, edge delivery, SSR/SSG rendering strategies, and direct third-party API integration without routing through BigCommerce's middleware.
Why Lighthouse Scores Matter Operationally
Google Lighthouse evaluates storefronts across four dimensions: Performance, Accessibility, Best Practices, and SEO. High scores across these dimensions correlate with:
- Faster page load times that reduce bounce rates and improve conversion
- Better Core Web Vitals scores that positively influence search ranking
- Accessibility compliance that expands the addressable customer base
- Security and modern web standard adherence that reduces technical risk
Catalyst's architecture is designed to achieve high Lighthouse scores by default: Next.js SSR and SSG minimize time-to-interactive, edge delivery reduces geographic latency, and the component architecture avoids render-blocking patterns that degrade performance scores on monolithic storefronts.
When Catalyst Is the Right Architecture
Catalyst makes the most operational sense for merchants who are running into specific Stencil limitations:
- Expanding product catalogs where storefront performance is degrading under catalog weight
- Unpredictable or high traffic volumes where edge delivery and scalable hosting matter
- Marketing team autonomy where campaigns are bottlenecked by developer dependency for content changes — Catalyst's Makeswift integration enables visual editing without code
- Integration requirements that need direct API-to-API connectivity rather than app marketplace workarounds
- Mobile-first strategies where Core Web Vitals on mobile devices are critical conversion variables
The Migration Path
Moving from Stencil to Catalyst is a frontend migration, not a full replatform. The BigCommerce backend — catalog, pricing, orders, customer data — stays in place. The work is rebuilding the presentation layer in the Catalyst framework and reconnecting integrations through the GraphQL API.
This is meaningfully less disruptive than a full platform migration, but it's not trivial. Frontend rebuild quality, SEO redirect mapping, integration reconnection, and performance validation all require structured execution.
Arizon Digital has executed BigCommerce Catalyst migrations for mid-market operators — see the full replatforming roadmap for what a structured migration looks like. Talk to us about whether Catalyst is the right next step for your storefront.