Flatsome vs Astra for WooCommerce: a store theme against a lightweight base

Pick Flatsome if you want a finished store design out of one purchase and nobody on the team will assemble pages from blocks. It ships its own UX Builder, a header builder, variation swatches, AJAX shop filtering, a free-shipping bar and catalog mode. One $59 license covers what would otherwise be several plugins. Pick Astra if someone will design the store in the block editor, or if you want the smallest possible theme layer under a builder you already know. The worse choice is the common one. Astra gets an Elementor starter template, imported and left as it is, with a marketing tag stack on top. That is the Brandstore demo, and it lost to Flatsome on score, LCP, blocking time, JavaScript and request count, and won only on DOM size and server time. Flatsome turns into the worse option once you need layouts its options cannot express, or once a later move off WordPress is likely.

Split by URL, the Brandstore demo's scripts are 572 KB of analytics and marketing tags (Google Tag Manager, Facebook's pixel and Google Analytics), 114 KB of WordPress core scripts, 94 KB of Elementor and 8 KB of Astra. Tags first, builder second, theme last. The astra theme directory sends 35 KB in all file types, which fits the vendor's claim of under 50 KB on the front end. Tracking tags cost the most main-thread time as well: Lighthouse charged 520 to 980 ms of scripting per run to the Facebook pixel and 300 to 535 ms to Tag Manager, against 11 to 25 ms to the theme. One homepage run is a natural experiment. The pixel did not load, JavaScript fell to 280 KB, blocking time dropped to 6 ms and the score rose to 57. LCP stayed at 10.2 seconds. The LCP element is an Elementor hero block, and the page carries 432 to 538 KB of fonts, 346 KB of them from Google's servers, which is exactly what Astra's local-fonts setting exists to avoid. Blocking time on this demo belongs to the tags; the slow paint belongs to the builder layout and its fonts. Flatsome's demo carries tags too, 183 KB of its 315 KB, so both totals describe a vendor's marketing setup as much as a theme.

• Third-party bytes: 44% of the Astra demo, 15% of Flatsome's
• Theme folder, all asset types: Astra 35 KB, Flatsome 147 KB
• Server response: Astra 50 ms from a Cloudflare cache hit, Flatsome 104 ms on Kinsta

Flatsome's median shop LCP was 7.2 seconds, and in every run the LCP element was a product image carrying Flatsome's lazy-load class, which waited 5.5 to 7.8 seconds before it started downloading. That is a setting, not the theme's weight: blocking time on the same page was 100 to 225 ms. Exempt the first row of products from lazy loading, as Flatsome speed optimization describes, and the shop page loses most of its delay. The homepage is less predictable. It scored 86, 49 and 55 across three runs, with LCP at 3.8, 9.1 and 9.0 seconds, so any single Flatsome PageSpeed test you run on your own store can land on either side of that gap.

In the Chrome UX Report for September 2026, 40.0% of 168,423 Astra origins passed all Core Web Vitals on mobile. LCP is where they fail: 44.3% pass it, against 89.3% for INP and 90.8% for CLS. That is the lowest pass rate of the six themes the report detects, below Blocksy at 50.3% and GeneratePress at 49.7%. A theme that ships 35 KB does not make the site on top of it fast. These are all WordPress origins running Astra, blogs and brochure sites among them, not WooCommerce stores alone. Flatsome has no row at all, because the report does not detect it, so no field comparison between the two exists from this source and any article quoting one has made it up.

Flatsome's regular license is $59 with six months of support, extendable to 12 months for $17.63 at the listing's current price, and future updates included; it has 270,594 sales and a 4.83 rating from 8,200 reviews. Astra is free on WordPress.org, with over a million active installs. Astra Pro, which adds a premium header and footer builder and WooCommerce extras, costs $69 a year as an add-on or $249 lifetime at the current offer. Over three years that is $59 against $207 for a store that keeps paying for Pro. The free theme alone is cheaper than either, provided the block editor covers the design.

Flatsome pages are stored as ux_* and row/col shortcodes, and the header lives in Flatsome's own header builder, outside page content. Switch themes and those shortcodes print as raw text, so leaving Flatsome means parsing them; the Flatsome to Next.js page covers that work. Astra's own lock-in is close to zero, because it stores almost nothing. The builder you put on it is another matter. Block-editor pages move cheaply, while Elementor pages sit in a JSON tree that needs its own extraction, which Astra to Next.js prices and Elementor WooCommerce speed fixes can postpone. If a headless frontend is on the two-year plan, Astra with the block editor is the cheaper start by a clear margin.

Lighthouse 12.6.1, mobile, three runs per template on October 18, 2026, from one machine in Spain. Flatsome's demo is its Classic Shop on Kinsta behind Cloudflare with WP Rocket; Astra's is Brandstore with Elementor, served from a Cloudflare cache. Hosting, plugins and content differ, and lab gaps under about 10 points are noise. If your Flatsome or Astra store is slow and you cannot tell theme from builder from tags, a free audit splits the bytes by layer, and fixed prices are on pricing.