WoodMart vs Shoptimizer for WooCommerce: what the lean theme buys you

Two of the three gaps are real. Shop pages scored 82 against 67 and product pages 77 against 63, both outside the roughly 10-point band that run-to-run noise covers in this dataset; home pages, 91 against 84, sit inside it. Blocking time is the starkest difference. Shoptimizer's product page blocked the main thread for 3 ms, WoodMart's for 728 ms, with 31 requests against 242. Shoptimizer was also the steadier demo: its home page ran 91, 90 and 91, while WoodMart's shop page swung from 64 to 89 between runs. These are lab numbers from one machine in Spain. HTTP Archive's technology report does not detect WoodMart or Shoptimizer, so there is no CrUX field data to hold them against.

Some of Shoptimizer's lead would not survive on a typical store. Put a 178 KB Google tag back on Shoptimizer's shop page and it would carry about 250 KB of script against WoodMart's 382 KB: the gap narrows and survives, because it sits in the theme layer, where Shoptimizer's own files come to about 2 KB and WoodMart's to 103 KB. Most of Shoptimizer's remaining script is WordPress core, 36 KB of it, jQuery included. A store running GA4, a Meta pixel and a reviews widget should read the demo's 73 KB as a floor, never as a forecast.

• No analytics tag on the demo: third-party bytes came to 10 KB, against 183 KB on WoodMart's, most of it Google's tag
• HTML served from Cloudflare's cache with a 57 ms median server response, while WoodMart's demo answered uncached in 219 ms
• Every stylesheet inlined into the HTML, so the shop page made no CSS requests at all where WoodMart's made 92
• CommerceGurus Turbo, the vendor's own caching and script-delay plugin, runs on the demo, and product images arrive through Cloudflare image resizing

Light JavaScript did not buy a fast Largest Contentful Paint. Shoptimizer's median was 4.2 s and WoodMart's 4.6 s, both past the 2.5-second line Google counts as good. On Shoptimizer's shop page the largest element is a promotional text bar, painted 3.6 to 3.8 seconds after its bytes were in hand, and Lighthouse flagged jQuery and jQuery Migrate as render-blocking on that page. WoodMart's flips between about 1.5 s and 5 s. If the metric failing in your Search Console report is LCP, a theme switch is the wrong fix. The hero image, fonts and render-blocking scripts hold that time on either theme; WoodMart speed optimization covers what tuning recovers.

Shoptimizer has no builder of its own. Layout options live in the WordPress Customizer, content goes into the block editor or any major builder, and the shop features come from CommerceKit, a bundled plugin: AJAX search suggestions, attribute swatches, free-shipping notices, order bumps and a mega menu, next to a sticky add-to-cart bar and a one-switch distraction-free checkout. The vendor says its demo content is built with Elementor, though only the home page shows Elementor markup; the shop and product pages load no Elementor scripts. The product page still carries 1,854 DOM elements, against WoodMart's 2,053-element median. Light script and a small DOM are separate properties. WoodMart goes the other way. It bundles WPBakery, supports Elementor and the block editor with 40+ custom elements in each, and adds a header builder and importable prebuilt websites. For a team that wants a different editorial layout per category without a developer, Shoptimizer is the weaker tool. Lock-in runs the opposite direction: Shoptimizer content kept in the block editor leaves the least to unpick later, and WoodMart on WPBakery leaves the most, as the WoodMart to Next.js migration notes explain.

WoodMart costs $69 once on ThemeForest, with lifetime updates and 6 months of support. Shoptimizer is a subscription sold on commercegurus.com: $99 a year at list price (the page showed $49 on a 24-hour sale on 18 October 2026), with updates and support tied to one domain per license and a 10-day refund window. Let it lapse and the theme keeps working, without updates. The product page publishes no renewal price, so we will not quote a three-year cost. For a single store the difference is small. Scenario: an agency with eight client stores pays 8 × $69 = $552 once for WoodMart, against 8 × $99 = $792 in the first year alone for Shoptimizer at list. WoodMart shipped 8.6.0 through 8.6.4 in 22 days; Shoptimizer shipped 2.9.6 through 2.9.9 between 18 August and 17 September 2026, after a 120-day pause, and its demo was running a 2.9.9 release candidate.

Tiered pricing is the clearest case. WoodMart builds in dynamic discounts with tiered pricing, frequently bought together, multiple wishlists and abandoned cart recovery, and CommerceKit's list overlaps on swatches and order bumps without naming any of those four. A wholesale store would rebuild them on Shoptimizer with plugins, each adding script to the product page that started at 3 ms of blocking time.

Take Shoptimizer for a single-brand store with a focused catalog, where revenue rides on product pages viewed on phones and the team is content with the block editor. Take WoodMart for a broad catalog that needs editorial layouts, for B2B pricing rules, or for an agency that would otherwise stack yearly per-domain licenses. WoodMart is the worse pick for a small direct-to-consumer brand with a few dozen products: it sends 75 script files to a product page that needs a gallery and a button. Shoptimizer is the worse pick when design range is the brief. If neither theme clears your speed target, read WoodMart vs a Next.js storefront; for a heavier alternative, WoodMart vs Flatsome. Measure before you switch, though: our free audit reads your own product and category templates, and the pricing page shows what a speed pass on the theme you already own would cost.