E-commerce
Choosing a WooCommerce theme: what actually matters past page 1 of Google
Theme "best of" lists optimise for affiliate revenue, not your sales. Here's what to actually check before you buy a WooCommerce theme.
LM
Linus Moses
Products Manager · December 7, 2021 · 4 min read
Search for "best WooCommerce theme" and you'll get a hundred listicles, mostly written for affiliate revenue. Themes get ranked by how big their commission is, not how well they sell your products. Here's what to actually evaluate before you click "purchase".
The four checks that matter
- Speed. Open the theme's official demo site in Chrome incognito. Run Lighthouse on the homepage and a product page. Mobile score under 70 → walk away. A slow theme will tank your conversion rate no matter how it looks.
- Page-builder dependency. Some themes need a specific page builder (Elementor Pro, Divi, WPBakery) to even render the homepage. That's a long-term lock-in. Prefer themes that use the WordPress block editor.
- Update cadence. Check the theme's changelog. Last update more than 6 months ago → walk away. WooCommerce and WordPress ship breaking changes every few months and an unmaintained theme will silently break.
- Real-world conversion. Ask the theme author for two live stores using their theme that aren't on the demo page. Compare your own goals to those stores. If they only show clothing and you sell electronics, the theme's UX may not transfer.
The boring categories that work
- Speed-first storefronts: Astra, Kadence, GeneratePress — light, fast, block-editor friendly. Pair with WooCommerce blocks for a clean stack.
- Fashion / lookbook: Flatsome, Botiga. Visual-first, plenty of demos.
- Headless commerce: Use a Next.js storefront against WooCommerce as a headless backend. Slower to set up, much faster end product.
Or skip the theme problem entirely
We build WooCommerce stores on a hand-coded base theme — no page builder, no theme lock-in, fully maintainable. The stack outlives any theme trend cycle.
Tell us what you sell. We'll come back with a quote and a recommended stack.