NextWoo
Performance

Astra speed optimization for WooCommerce

Astra is not usually the problem, which makes it the wrong place to start. This is the order to check things so you spend the effort where the bytes are.

Astra storefront weighed as three separate asset layers on a performance dial

Most Astra speed optimization advice assumes the theme is heavy. Astra is not: it ships under 50KB of its own assets, uses vanilla JavaScript rather than jQuery, self-hosts Google Fonts and lazy-loads media out of the box. That changes the whole diagnostic. If an Astra store is slow, the weight is arriving from somewhere else, and hours spent tightening theme settings will move a number that was never the bottleneck. The order below is the one we work in, cheapest and most diagnostic first, and it names the point where tuning stops paying.

01

Weigh the three layers before changing anything

Open the network panel on a product page, disable cache, and sort by transfer size. Then attribute every request to one of three buckets: theme, page builder, plugins. Fifteen minutes, and it decides everything that follows. On a healthy Astra store the theme bucket lands under 50KB. If your total page weight is 2MB and the theme is 40KB of it, the useful work is entirely in the other 1.96MB — and a consultant who proposes theme tuning after seeing that split has not looked.

  • Disable cache and record transfer size, not resource count
  • Attribute each request to theme, builder or plugin
  • Record the number before any change so you can prove the delta
  • Repeat on a category page — the mix is usually different
  • Compare a Starter Template page with a page built in the block editor on the same site
  • If the theme is under 10% of transferred bytes, take theme tuning off the list
02

The Performance panel most Astra sites never opened

Astra has settings that are off by default under WordPress Dashboard → Astra → Settings → Performance, and a surprising share of stores have never been there. The one that matters most is loading Google Fonts locally: it downloads the fonts to your own server, which removes a third-party connection from the critical path and settles the GDPR question about Google's font CDN at the same time. This is a five-minute change with a measurable effect on LCP for any store whose headline text uses a webfont; on a system font stack it changes nothing. Check it before anything more ambitious.

03

Astra Pro modules are opt-in, so audit what you opted into

The astra-addon plugin ships as a bundle of modules that can be enabled and disabled individually, and that control is the main reason Astra stays lean when it does. It also means the modules are enabled by whoever set the site up, often all of them, and then never revisited. Go through the list and turn off anything the store does not visibly use. Each disabled module removes its assets from every page load, not just the pages that would have used it. A module nobody can point at in the live storefront has no defence for staying enabled. The usual finds are a slider module for a slider removed two years ago, and a WooCommerce feature nobody can locate on any page.

04

Identify your builder, because that is where the bytes are

Astra ships no builder, so whatever is producing your pages is a separate product with a separate performance profile. Elementor stores carry the most weight and also have the most recoverable headroom: its performance features are off by default, and turning on conditional Swiper loading alone strips 26.7KB of CSS from pages that have no carousel. The Elementor WooCommerce speed fixes walk through the rest of that settings list and the template cleanup after it. Spectra and core blocks are the lightest case and usually need nothing. Beaver Builder sits in between. Work out which one you have before reading any generic advice, because the fixes do not transfer between them.

  • Elementor: enable the performance features before concluding anything
  • Spectra and core blocks: usually already fine, look elsewhere
  • Beaver Builder: check module-level asset loading
  • Mixed sites: measure a page from each builder separately
05

What the Starter Template brought with it

Starter Template imports install more than a design: a slider plugin, a forms plugin, a widget pack, a builder. The import needs PHP memory raised to at least 256MB to complete, which tells you how much it puts in place. Audit that list against what the storefront visibly does today.

06

Caching sits on top of the problem, not in place of it

A page cache serves stored HTML and improves your lab scores immediately. It does not reduce the CSS and JavaScript the browser still parses and executes, which is what INP measures, and it does nothing for the first visit to an uncached URL — on a large catalog, most product pages. Good LCP with poor INP in field data is the signature: cached HTML arriving fast, then the main thread stalling on scripts the cache never touched.

07

The point where tuning Astra stops paying

Be honest about the ceiling. If the theme bucket is already under 50KB, every remaining optimization is happening in the builder and plugin layers, and there is a floor below which those cannot go while they remain installed. When the store has done the settings pass, disabled unused modules, enabled the builder's own performance features and fixed images, and field data is still red on mobile, further tuning is not worth the time — the remaining weight is structural. That is the point where replacing the frontend becomes a real option rather than an upsell, and not before it. What that project extracts, from Starter Template pages to Astra Pro custom layouts, and what sets its price is covered on the Astra to Next.js migration page.

08

Fix the images before blaming any of this

The least interesting cause is the most common one, which is why it closes the list. An unoptimized hero image, a product gallery serving 2000px files to a 400px viewport, or a logo shipped as a 300KB PNG will dominate every measurement discussed above. Serve WebP or AVIF, size images to their display dimensions, set explicit width and height to stop layout shift, and mark the hero with fetchpriority so it does not queue behind decorative assets. Until that has been done, theme tuning is a distraction from the thing actually costing you the metric. On a good number of Astra stores this alone closes the gap, and it costs an afternoon.

Frequently asked questions

Still have questions?

Reach out and we'll get back to you within 24 hours.

Contact us
Is Astra actually a fast theme?

Yes. It ships under 50KB of its own assets, uses vanilla JavaScript rather than jQuery, self-hosts Google Fonts and lazy-loads media. Tuning the theme is therefore rarely where an Astra store's problem sits.

What is the first Astra setting to change for speed?

Loading Google Fonts locally, under Dashboard → Astra → Settings → Performance. It removes a third-party connection from the critical path and takes about five minutes.

Is my Astra store slow because of the theme or the page builder?

Usually the builder or the plugins. Weigh them separately in the network panel with cache disabled. If the theme bucket is under 50KB of a 2MB page, the theme is not the target and theme tuning will not move the number.

When should I stop optimizing Astra?

After the settings pass, unused Astra Pro modules disabled, the builder's own performance features enabled and images fixed. If field data is still red on mobile after that, the remaining weight is structural rather than a tuning problem.

Related reading
  • Astra to Next.js

    Astra to Next.js migration for WooCommerce: extracting Starter Template and Spectra pages, rebuilding Astra Pro layouts, redirects and what sets the price.

  • Elementor WooCommerce slow

    Elementor speed optimization for WooCommerce: the Features settings to switch on, how to measure the builder layer, where WP Rocket stops and when to rebuild.

  • Flatsome vs Astra

    Flatsome vs Astra for WooCommerce: Astra's own code is 35 KB of an 853 KB-script demo. When the $59 store theme wins, and when the free lightweight one does.

See how many sales your store is losing

Start with a free speed audit. You'll get your store's real numbers and an honest recommendation — even if it's "you don't need us".

Anything you already suspect — checkout feels slow on phones, the category pages crawl, you were told the theme is the problem. Guesses are useful; we check them.

No sales call — you'll get a written report with your store's numbers.

By requesting an audit you accept our Privacy policy and Terms of service. We may publish an anonymised summary of the findings as an example of our work. We never name your business without your written consent.