WoodMart vs Flatsome: which WooCommerce theme to pick, measured

Read the score as a tie. Flatsome's Classic Shop home page scored 86, 49 and 55 on three runs ten minutes apart, and WoodMart's shop page went 64, 89, 67. A 4-point gap in the medians sits well inside that swing. Total Blocking Time is where the demos separate: 432 ms for WoodMart on the shop template against Flatsome's 161 ms, and 728 ms against 148 ms on the product page. Home pages were close (552 and 472 ms), because Flatsome's Classic Shop home runs a heavy banner layout. The JavaScript totals understate the gap, because they include each demo's own tracking: about 180 KB of each is Google's tag. With the tags removed WoodMart's shop page sends roughly 204 KB of script in 74 files where Flatsome's sends 118 KB in 27, plus 92 separate stylesheets against Flatsome's 5. The themes' own files account for 103 KB and 36 KB of that (median across templates); WordPress core and WooCommerce scripts make up most of the rest. TBT is a lab metric and it is not INP. Still, a phone that is busy parsing scripts during load answers the first tap late, and on a store whose traffic is mid-range Android phones that is the number to weigh.

Flatsome's worst number has the cheapest fix on this page. On the demo's shop page the largest element is the first product card's image, and Flatsome's own lazy loading swaps it in from a data-src attribute, so the browser cannot find it in the HTML. Lighthouse logged 5.5 to 7.8 seconds of load delay before that image was even requested. Excluding above-the-fold images from lazy loading is a settings change, covered in Flatsome speed optimization. WoodMart's LCP has a different shape. It is bimodal, about 1.5 s on some runs and about 5 s on others, on every template, and on the slow runs the image had already arrived and then waited up to 4.3 seconds to be painted. That points at a busy main thread rather than a missing preload, and no single toggle fixes it; the WoodMart speed optimization guide works through module scoping and script delay. One more caution: the LCP element on WoodMart's home page is its 369 × 53 logo, so the 1.5 s home LCP flatters the theme.

WoodMart's $10 premium buys features that cost real money as plugins. Its ThemeForest listing names multiple wishlists, frequently bought together, dynamic discounts with tiered pricing, abandoned cart recovery and quick view, all built in. Flatsome covers variation swatches (added in 3.14.0), a catalog mode that hides cart and checkout, and a quick Buy Now button (3.19.0), while its demo loads Flatsome's styling for the separate YITH Wishlist plugin. A wholesale store that needs tiered pricing is the clearest case for WoodMart. On Flatsome it would take a pricing plugin plus a bundles plugin, each bringing scripts to the product page and narrowing the 580 ms blocking-time gap measured there. If you need none of those features, WoodMart's extra weight is not worth carrying.

Lock-in is the cost nobody prices at checkout. Flatsome pages are built in UX Builder, the theme's own drag-and-drop editor, and stored as ux_* and row/col shortcodes that no other theme renders. Switch themes and those pages turn into bracketed text; Flatsome to Next.js describes parsing them back into components. WoodMart bundles WPBakery, whose [vc_row] shortcodes carry the same problem, but it also supports Elementor and the block editor with 40+ custom elements in each. Its custom blocks still need the theme to render, yet block content is stored as markup with structured attributes, which converts more predictably than nested shortcodes. If a redesign or a headless move is likely within a few years, build WoodMart on the block editor and never on WPBakery; the WoodMart to Next.js migration is cheapest from there, and WoodMart vs a Next.js storefront covers when that move is worth making at all.

Both are one-time ThemeForest purchases with future updates and 6 months of author support: $59 for Flatsome, $69 for WoodMart. Flatsome lists 270,594 sales and a 4.83 rating from 8.2K reviews; WoodMart lists 119,822 sales and 4.91 from 3.7K. WoodMart ships in bursts, five releases from 8.6.0 on 14 September to 8.6.4 on 6 October 2026. Flatsome shipped eight between 3.20.4 in December 2025 and 3.20.11 on 22 September 2026, roughly one a month. Neither cadence decides anything on its own. More frequent releases mean more update testing on a store with custom templates.

Every number above describes two websites, not two themes. Flatsome's demo runs on Kinsta behind Cloudflare with WP Rocket; WoodMart's runs WPBakery and WP Rocket behind Cloudflare and loads a Cloudflare bot-check script that adds long tasks of its own. CrUX field data by theme comes from HTTP Archive's technology report, which detects neither of these two, so nothing from real visitors exists to check this lab work against. All runs came from one machine in Spain within half an hour. A store with 3,000 products, a review app and a chat widget will not reproduce either demo by installing the theme.

Pick Flatsome for a catalog store on ordinary hosting whose buyers arrive mostly on phones, and exclude the first row of product images from lazy loading on day one. Pick WoodMart when tiered pricing, bundles or multiple wishlists are on the roadmap. Build it on the block editor. WoodMart is the worse choice for a small store that needs none of its extras, because it pays the main-thread cost of 74 script files for features nobody clicks. Flatsome is the worse choice when a migration is already planned: UX Builder content has to be converted page by page, and that bill lands later. Already running one of the two and failing Core Web Vitals? A free audit measures your own templates instead of a vendor demo, and pricing lists what the fixes cost.