WoodMart vs Blocksy for WooCommerce: an all-in-one store theme against a block theme

Take Blocksy if the store sells a few hundred products at fixed prices, someone on the team is comfortable in the block editor, and buyers mostly arrive on phones. Its demo blocked the main thread for 91 ms against WoodMart's 552 ms, and its own code came to 17 KB of JavaScript against 103 KB. Take WoodMart if the business depends on quantity breaks, frequently-bought-together offers or abandoned cart emails, because those come with the $69 license and Blocksy's feature table does not list them at any tier. WoodMart is the worse purchase for a small direct-to-consumer brand that will never switch those modules on, since it pays the script cost of features nobody uses. Blocksy is the worse purchase for a wholesale catalog. There the plugins needed to match WoodMart would each add scripts to a product page that started at 91 ms.

The two demos are slow at opposite ends of the page load. WoodMart drew its first content in 1.3 to 1.6 seconds on every template; Blocksy took 2.9 to 3.1. After that the order flips. WoodMart's main thread did a median 5.2 seconds of work per run against Blocksy's 2.3, and Total Blocking Time on the product page was 728 ms against 91 ms. That page also made 242 requests to Blocksy's 53 and carried 2,541 DOM elements to 677. Part of WoodMart's weight is the vendor's own tracking. Google's tag accounts for 178 KB of the demo's 382 KB of JavaScript, and Blocksy's demo loads no tags at all. Even with the tag removed WoodMart sends about twice the script, and its theme files account for 103 KB against Blocksy's 17 KB, Blocksy Companion included. On Blocksy's demo the most expensive script is not the theme. Cloudflare's bot-check script took 290 to 390 ms of scripting per run, while Blocksy's main bundle took 40 to 70 ms. Blocking time is a lab number and Google ranks on INP from real visitors. Still, a phone that is busy parsing script when the shopper taps a size swatch answers late, and that is where WoodMart speed optimization starts: loading each module only on the templates that use it.

On Blocksy's shop page the largest element is the first product image, and its markup carries fetchpriority=high and loading=lazy at the same time. The file arrived within 0.3 seconds of being requested, then waited 3.8 to 4.6 seconds to be painted while Lighthouse flagged jQuery and three Blocksy stylesheets as render-blocking, for a median LCP of 5.5 seconds. Google's threshold is 2.5. WoodMart's shop page missed it too, at 5.1, 1.7 and 5.6 seconds across three runs. One slow run waited on a lazy-loaded product image; the other had its 1,900-pixel banner downloaded and then held for 4.3 seconds behind the main thread. On either theme, take the first row of product images out of lazy loading first.

WoodMart's listing names frequently bought together, dynamic discounts with tiered pricing, abandoned cart recovery, free gifts and a price tracker. None of the five appears in Blocksy's plan comparison table, free or paid. Elsewhere the lists overlap, since Blocksy's Business and Agency plans cover swatches, quick view, AJAX filtering, a wishlist, compare, size guides, brands and a free-shipping bar. The decision rests on those five. A B2B store selling in case quantities needs tiered pricing on day one, and on Blocksy that means a separate pricing plugin plus an email tool for abandoned carts, each with its own license and its own scripts. A boutique selling 80 products at list price needs none of them, and WoodMart's extra 86 KB of theme JavaScript buys it nothing.

Blocksy's Personal plan costs $69 a year for one site and leaves out the Shop Extra extension, which is where every WooCommerce feature above lives. The first plan that includes it is Business: $99 a year or $299 lifetime, for up to 10 sites. WoodMart is $69 once, with future updates and six months of support. Over three years a single store pays $69 for WoodMart against $297 for Blocksy Business on annual billing. A shop that needs no swatches or quick view can stay on the free theme, which already has AJAX add-to-cart and a variation image gallery.

Exit cost favors Blocksy by a wide margin. WoodMart's own demo is built in WPBakery, which stores pages as [vc_row] shortcodes that print as raw text once the plugin is gone; WoodMart to Next.js covers what extracting them costs. A WoodMart store built on its Gutenberg blocks is cheaper to leave, though its 40+ custom blocks still need the theme to render. Blocksy pages are plain block markup in post_content. Two things do not travel. The header and footer builders keep their settings in theme mods, and starter sites bring their own block plugins: the Modern Shop homepage is built with Stackable, a third-party block library, so importing it adds a second dependency. Moving a Blocksy store to a headless frontend resembles the Kadence to Next.js case, cheap to extract and hard to justify on speed alone.

Blocksy shipped 37 releases in 2026 up to 2.1.60 on October 15, roughly one a week. WoodMart shipped 8.6.0 through 8.6.4 between September 14 and October 6. Blocksy's own demo still runs 2.1.29 from February 18, so its numbers describe a build eight months older than the one you would install.

Only one of the two can be checked against real visitors. Blocksy's row in the Chrome UX Report reads 50.3% for September 2026: that share of its 23,072 origins had good LCP, INP and CLS on phones. WordPress as a whole sits at 48.3% and WooCommerce stores at 39.3%. Those origins are every site HTTP Archive detected running Blocksy, blogs included, and the report does not detect WoodMart at all. Every lab figure above compares two websites with different hosting, plugins and content, not two themes in isolation. If your WoodMart store fails Core Web Vitals and you are weighing a switch, a free audit measures your own templates first, and pricing lists what a speed pass on the current theme costs. For WoodMart against another ThemeForest store theme, see WoodMart vs Flatsome.