Kadence vs Shoptimizer for WooCommerce: a block theme against a store-only theme

Kadence's product page scored 59 on all three runs, and the reason sits in its request list. Of 479 KB of JavaScript, 347 KB is Google's recaptcha__en.js from gstatic.com, loaded by the iThemes Security Pro plugin to protect the product review form further down the page. That one file made third-party bytes 53% of the page, against 18% on the shop page, and Lighthouse charged it 904 to 972 ms of script evaluation per run, more than any other script on the page. The gallery image, which is the LCP element, was requested 1.1 to 1.3 seconds into the load and then waited about 7 seconds to be painted, for a median LCP of 8.5 seconds. Lighthouse still reported 0 ms of Total Blocking Time on every run, which is a reminder that simulated metrics can disagree with each other on the same trace. We did not re-run the page without the CAPTCHA, so the exact number of points it costs is unknown; the shop page is the closest estimate. This is a demo-builder choice, not the theme. A real store can load its CAPTCHA only when someone opens the review form, or use a honeypot field instead, and get most of that time back on either theme.

Without the CAPTCHA the two demos look alike. Kadence's shop page sent 78 KB of JavaScript against Shoptimizer's 73 KB, with 0 ms of blocking time against 19 ms, and it rendered 921 DOM elements to Shoptimizer's 1,861. Shoptimizer's advantage is delivery. Its HTML came from Cloudflare's cache in 97 ms, while Kadence's demo answered uncached in 181 ms, and Kadence loads its fonts through Google's WebFont loader, 100 KB of them against 48 KB. The theme layers are both small: about 19 KB on Kadence's shop page, counting Kadence Pro's infinite scroll, and about 2 KB on Shoptimizer's.

In the Chrome UX Report for September 2026, 49.8% of 35,642 origins running Kadence passed all Core Web Vitals on mobile, with LCP the weak metric at 58.3% against 88.9% for INP and 88.6% for CLS. In the same Chrome UX Report month, WordPress origins as a whole passed at 48.3% and WooCommerce stores at 39.3%, which puts Kadence at the WordPress average and above the WooCommerce figure; our WooCommerce Core Web Vitals statistics break those two down. The population is every WordPress site HTTP Archive detects running Kadence, blogs and brochure sites included, so it is not a store benchmark. Shoptimizer has no row, because the report does not detect it. Its lab lead is the only evidence there is, from one demo on a well-cached host. Any claim that Shoptimizer stores pass Core Web Vitals more often than Kadence stores has no public data behind it.

The Kadence theme is free on WordPress.org, at version 1.5.2 with 500,000+ active installs, and it runs WooCommerce without any paid add-on. The demo's product page is not the free theme, though. Its gallery, variation swatches and size chart come from Kadence Shop Kit (41 KB of script on that page), and its sticky add-to-cart bar, mega menu and shop infinite scroll come from Kadence Pro. Liquid Web now sells both inside one plan: Pro at $299 a year, which also bundles security, backups and memberships, or Elite at $499 for agencies. The pricing page shows no smaller store-only option and no site count for Pro. Shoptimizer's $99 a year includes CommerceKit: AJAX search suggestions, attribute swatches, free-shipping notices and order bumps. For a single store that wants a demo-like product page, Kadence Pro is the worse buy by $200 a year. The free Kadence theme is the better one for a store that needs none of those features, or that fills the gaps with free plugins and accepts their script weight.

Kadence Blocks store content as block markup in post content, readable by any parser, which is why Kadence to Next.js is one of the cheaper migrations off WordPress; its header and footer builder lives in theme mods and has to be transcribed by hand. Shoptimizer keeps its layout in the Customizer and ships no builder, so its exit cost depends on what you write content in. Block editor pages leave as cleanly as Kadence's. The trap is the demo import: Shoptimizer's demo home page is built with Elementor, and importing it brings Elementor's JSON page data along.

Kadence shipped 1.4.3 on January 8, 2026, then five more versions through 1.5.2 on July 24, nearly three months before this test. Its demo still runs 1.4.2 from November 2025. Shoptimizer's demo runs a 2.9.9 release candidate, after a 120-day gap between 2.9.5 in April and four releases from August 18 to September 17. Neither demo reflects the version you would install today.

Take Kadence when the site carries a blog, guides or campaign pages designed in blocks, or when the budget points to the free theme, whose field record is the better documented of the two. Take Shoptimizer for a single-brand catalog that wants swatches, order bumps and a sticky cart out of the box, where $99 a year undercuts Kadence's $299 bundle. Kadence on Pro is the worse choice for a store that buys the bundle only for Shop Kit. Shoptimizer is the worse choice for content-led stores, because its feature budget goes to the cart and none of it to layout. For Shoptimizer against heavier rivals, see WoodMart vs Shoptimizer and Shoptimizer vs Flatsome. If your store already runs one of these and fails Core Web Vitals, a free audit splits your own scripts by source the way this page split the demos.