Astra Theme Speed: The Settings, the Order and the Ceiling

What Astra itself puts on the wire

Brainstorm Force says Astra needs less than 50 KB of resources, loads a site in 0.5 seconds and is fully compatible with HTTP/2. Treat all three as marketing, because none comes with a test you can repeat. What the code shows is more useful. Astra 4.14.0, the September 24, 2026 release, is a classic Customizer theme whose own front-end scripts declare no jQuery dependency, with one exception tied to WooCommerce. That matters: a theme that never asks for jQuery leaves one less blocking library in your page's head.

Inline CSS is not automatically bad. On a visitor's first page it saves a round trip, and with full-page caching the cost is a few extra kilobytes per HTML file. It starts to hurt on sites where people read five or six pages per visit, because each page carries the same block of styles again. That is the case for file generation, and it is the reason to check which tier you own before promising anyone a fix. Our Astra review covers the rest of what separates free from Pro.

Why a 50 KB theme ships a heavy homepage

The weight arrives on day one, through the Starter Templates plugin (astra-sites, over 1,000,000 active installs on wordpress.org). A template is a finished site built in a particular page builder, so importing one quietly chooses your builder, your section layouts and often a handful of supporting plugins. The paid toolkits add more: Spectra Pro and Ultimate Addons for Elementor come with the Essential Toolkit + AI bundle, and the Business Toolkit adds SureForms Agency. Every one is a reasonable product. Together they decide your page weight far more than the theme does.

• Elementor plus Ultimate Addons for Elementor. Each widget pack brings its own stylesheets and scripts, and every section, column and widget is another wrapper in the markup. Our notes on an Elementor site that crawls cover that layer in depth.
• Spectra blocks. Lighter than a visual builder in most cases, but carousel and animation features still load code on the pages that use them. See Astra with Gutenberg for how Spectra and the theme divide the work.
• Mega menus built from templates. Astra Pro can drop Elementor, Beaver Builder, Divi, Brizy or block templates into menu dropdowns. That puts a builder layout inside your header on every page, opened or not.
• Demo leftovers. Hero sliders, counters, popups and form plugins that came with the template and stayed active after the pages using them were deleted.
• Store extras. Astra Pro's quick view, infinite pagination and image zoom earn their keep on shop and product pages and nowhere else. The Astra WooCommerce guide shows which to keep.

None of this is a reason to avoid Astra. It is a reason to stop judging the theme by a PageSpeed Insights score earned by its passengers. Before changing anything, find out which plugin each heavy file belongs to. The WordPress performance guides explain how to read a waterfall, and our list of themes that ship the least CSS and JavaScript shows where Astra starts relative to its rivals.

Eight passes over an Astra site, cheapest win first

Work through these in order, one change at a time, retesting after each. The order matters: early steps are free and safe, later ones touch layouts and need a visual check.

1. 1

   Measure the templates, not just the homepage

   Run field data and lab tests for the home page, a service page, a blog post and, on a store, a product page. Astra sites often score well on posts and badly on the template-built homepage. Our guide to reading PageSpeed Insights for a theme explains which numbers to trust.

2. 2

   Clone the site to staging

   Astra's 4.13 releases produced fatal errors and at least one advised rollback, so every speed change and every update gets tried on a copy before the live site.

3. 3

   Load Google Fonts locally

   Turn on Load Google Fonts Locally under Astra > Settings > Performance, preload only the font used above the fold, and cut unused weights in the Customizer's typography settings. If text vanishes afterward, see Astra fonts not loading.

4. 4

   Decide where the Customizer CSS lives

   With Astra Pro, test CSS File Generation against inline output on a multi-page visit. Without Pro, leave it inline and let your caching layer do its job. Purge caches after Customizer changes, or read Astra CSS not updating.

5. 5

   Remove what the starter template left

   List every active plugin and every page that uses it. Deactivate plugins with no users, delete demo pages, popups and unused global sections, then retest.

6. 6

   Put the builder on a diet

   Switch off add-on widgets nobody placed, replace sliders with a single image, flatten nested sections, and drop scroll animations on mobile.

7. 7

   Fix the hero and the header

   Make the largest above-the-fold image a real, correctly sized img element that is never lazy-loaded, and give the logo fixed dimensions so the header cannot jump.

8. 8

   Update on a schedule, with a way back

   Keep Astra, Astra Pro and the builder updated together on staging, retest the same templates, and keep a backup that can restore the previous versions in minutes.

Core Web Vitals on Astra: hero sections, header rows and the hamburger

Largest Contentful Paint: usually a builder background

On most starter templates the LCP element is a full-width hero, and builders love to set that hero as a CSS background image. The browser cannot find a background image until it has downloaded and parsed the stylesheet that names it, so the most important picture on the page is requested late. Swapping it for an image element with explicit width and height, served in a modern format at phone size, is often the largest single LCP gain on an Astra site. The mechanism is laid out in slow LCP on WordPress themes.

Cumulative Layout Shift: the header that changes shape

Astra's header builder gives desktop, tablet and mobile their own above, primary and below rows, and each can be a different height. Shifts come from a logo with no dimensions, a transparent header that later gains a background, a Pro sticky header that changes size when it attaches, and Google Fonts swapping in after first paint. Test at 921 pixels, where the toggle menu takes over, as well as on a phone. Layout shift in WordPress themes walks through the checks.

Interaction to Next Paint: menus and borrowed scripts

INP measures how fast the page responds after a tap. On Astra the usual culprits are not the theme's menu script but what competes with it: a mega menu built from a builder template, chat widgets, cookie banners and tag manager scripts all queuing work on a phone's main thread. If the hamburger feels slow or opens empty on real phones, start with Astra mobile menu not working and the header builder repair notes.

For how each metric behaves on WordPress compared with a coded front end, see the side-by-sides on LCP, CLS and INP.

A slow Customizer is not a slow website

One complaint reaches us described as a speed problem when it is something else. Under WordPress 7.0, one user measured about 127 seconds for customize.php with Astra 4.13.x, WooCommerce and Elementor Pro active, and the Customizer never finished loading. Visitors never see that screen, so caching plugins and image compression will not touch it. It is an admin compatibility problem between the theme, the builder and WordPress core, and the fix belongs to updates and conflict testing, not to speed settings.

The same goes for the report that Astra 4.13.1 caused memory problems which broke GPay and Apple Pay at checkout. A memory leak can make pages slow, but the cure is a version change, not a tune-up. When settings refuse to save, start at Astra Customizer not saving. When pages broke after an update, see Astra layout broken after update. Everything else Astra-specific is in the Astra repair hub.

Six limits no Astra setting reaches

• The builder's markup. Astra cannot thin the wrappers Elementor or another visual builder writes. Only rebuilding the page with fewer sections does that.
• CSS files without Pro. The current comparison lists CSS File Generation under Astra Pro, which on its own covers up to 3 websites at $69 a year as of October 2026. Details on Astra pricing.
• Breakpoints. Moving the 921px or 544px switch takes PHP filters in a child theme, which our Astra developers add routinely.
• Uncached requests. Logged-in users, carts and checkouts still run PHP and database queries on every view, whatever the theme does.
• Third-party scripts. Analytics, chat, review badges and ad tags load from other companies' servers on their own schedule.
• Separate update cycles. Astra, Astra Pro, Starter Templates, the builder and each add-on update independently, so a fast site can turn slow on a Tuesday without anyone touching it.

Astra can keep its own code small. It cannot vote on what you install next to it.

If you have already worked through the passes above and the numbers have stopped moving, the floor is probably in this list rather than in a setting you missed. That is useful knowledge. It tells you whether to keep tuning or to start comparing options, and our theme speed optimization work always ends with a plain statement of which one applies.

When speed is the reason to leave Astra for Next.js

For a brochure site that already passes Core Web Vitals, keep Astra and keep it tidy. The case for a rebuild starts when speed is tied to revenue and the limits above are the reason you cannot get there: a lead-generation site losing mobile visitors, a store whose product pages need a builder to look right, or a site where every update risks a regression. Our Astra vs Next.js comparison lays out those trade-offs row by row.

A Next.js site removes the mechanisms rather than tuning them. Pages are prerendered before anyone visits and served from a CDN, next/image sizes and converts the hero automatically, next/font self-hosts the typeface with no setting to forget, and React Server Components keep most JavaScript off the phone. It costs more up front and needs a developer for structural changes. Moving Astra to Next.js explains what happens to Customizer settings and Spectra blocks, and Elementor content migration covers builder pages.

The editing side is Athena CMS: plain fields and a real preview, with Argus flagging pages that turn slow and Picasso making sure every image is described and sized. Not sure which side of the line you are on? A free site audit measures the site you actually run, and the broader WordPress vs Next.js speed page explains the gap. Browse more reviews and guides in the WordPress themes section.