WoodMart vs XStore: two feature-heavy WooCommerce themes, measured

On the vendors' own demo stores, WoodMart posted a median mobile score of 67 and XStore 29, with 552 ms of Total Blocking Time against 2,671 ms. Gaps under about 10 points are noise in this dataset. Thirty-eight points is not. XStore's homepage was its worst template at 3,163 ms of blocking time, and the median template carried 3,409 DOM elements to WoodMart's 2,053. Lighthouse charges most of XStore's scripting to the WordPress core scripts in wp-includes, jQuery among them: 1.2 to 2.6 seconds per run, against 0.3 to 1.05 seconds on WoodMart. Theme and plugin code built on jQuery executes inside that file, so the attribution names no single culprit. Request count pointed the other way: WoodMart made 219 requests to XStore's 125 and still finished well ahead. One limit on all of this: TBT is a lab stand-in, not INP. It counts main-thread work during load, while Google ranks on how fast real taps get answered, and a store selling mostly to desktop visitors will feel this gap far less than one selling to phones.

Both demo totals include the vendor's own tracking, so the fair comparison is each theme's own code. Split by URL, XStore's 1,046 KB of JavaScript is 323 KB of analytics and marketing tags, 349 KB of builder and slider code (Elementor, Pro Elements and about 220 KB of Slider Revolution) and 257 KB from the theme and its companion core plugin. WoodMart's 382 KB is 178 KB of tags and 103 KB of theme. Remove the slider and the tags from both and XStore still sends two and a half times as much theme JavaScript. That part comes with the purchase. The slider does not have to: a store that never activates Slider Revolution never pays for its 220 KB.

WoodMart's median LCP of 4.6 seconds hides a split. Every template produced fast runs between 1.4 and 1.7 seconds and slow ones near 5, with nothing in between. In four of the five slow runs the LCP image had already downloaded, and what grew was render delay, from 0.2–0.6 seconds to 3.3–4.3 seconds. The main thread held up the paint. Its homepage scored 84 partly because the LCP element there is a 369 × 53 px logo. If your homepage opens on a full-width hero banner, do not expect that 84. The listing promises 90+ PageSpeed scores; the best single run on the vendor's own demo was 89, on the shop page. XStore had no fast mode at all: its product image waited 6.9 to 10.7 seconds before it started downloading.

XStore's $59 regular license lists 13 premium plugins free with the theme, among them Slider Revolution, WPBakery Page Builder, Essential Grid, Master Slider and Quform. WoodMart's $69 license includes two, WPBakery and an image optimizer. A build plan that already calls for a premium slider, a grid plugin and a form builder makes XStore cheaper than buying those separately, and that is the strongest reason to pick it. The catch is that bundled licenses are activated through the theme. Leave XStore and each plugin loses its update path, so a migration has to replace, buy or retire every one of them; the XStore to Next.js page walks through that inventory. A store that would never have bought those plugins is paying for the bundle in main-thread time and getting nothing back.

WoodMart works with Elementor, WPBakery or Gutenberg, and its own demo runs WPBakery. The builder is picked once and paid for at migration time. Block-editor content sits in post_content as structured blocks. WPBakery leaves vc_row shortcodes and Elementor leaves a JSON tree in _elementor_data, and both have to be parsed before anything can be rebuilt; the WoodMart to Next.js page covers that extraction. XStore lists the same three builders as compatible, but its flagship demo is the Elementor one, and product and archive presentation lives in XStore's own options on top of whichever builder you use. Two extraction paths instead of one. A new store started on WoodMart with the block editor carries the smallest bill if it ever moves.

The XStore demo ran 9.7.8, released September 8, 2026. Version 9.7.9 followed on October 8 and 9.7.10 on October 15, so on the day we measured, the vendor's own demo was two releases behind its listing. WoodMart's demo ran 8.6.4, the version its listing shipped on October 6. Frequent releases help a store that stays on the theme, and they date this data: remeasure the current XStore build on staging before treating speed as settled.

These rows describe two websites, not two themes. WoodMart's demo runs WPBakery and WP Rocket behind Cloudflare. XStore's runs Elementor, Slider Revolution and WP Rocket on an nginx server at Hetzner in Germany with no CDN, and every run came from one machine in Spain, so a US shopper would see different server times. Lighthouse 12.6.1, mobile, three runs per page, October 18, 2026. XStore's product page returned no LCP in two of four runs, so its product row, which supplies the LCP and TBT figures in the table, is the median of the two valid runs. Neither theme is detected in the Chrome UX Report's technology data, which leaves no field pass rate to check the lab against.

For a store where most orders come from phones, WoodMart is the better choice: lower blocking time on every template, less than half the theme JavaScript, and a builder option that keeps a future migration cheap. XStore suits one profile. That store needs Slider Revolution, Essential Grid and a form plugin, intends to stay on WordPress for years, and accepts heavier pages in exchange for the bundle. It is the worse choice for a catalog where mobile speed decides sales, and for any store already planning a headless frontend within two years, because the bundle turns into a list of licenses to replace. If you already run WoodMart and the numbers are red, WoodMart speed optimization sets the order of work, a free audit finds the template that is costing you, and fixed prices are on pricing.