Avada Speed Optimization: Wizard First, Then the Demo You Imported

A theme that admits content decides the score

ThemeFusion's speed documentation contains a sentence most vendors would edit out. Avada, it says, gives you the ability to get good speed test scores on most tools, but 'user content will primarily dictate how fast your site will perform.' That is the most useful thing anyone has written about Avada performance, and it comes from the people who make it. Their Performance Wizard page makes no numeric claims at all, only that critical CSS improves 'page load and render time.' So there is no vendor score to chase here, only your own.

That candor also explains where the work goes. Avada brings a page builder, a layout builder, a header builder, forms, a WooCommerce builder and six bundled premium plugins. Every one of those features is something the theme might load. The settings below exist to stop it loading what a page does not use, and the steps further down put them in a safe order. Measure before you touch anything, using our WordPress theme speed test method, so every later change has a baseline.

What the Performance Wizard does, and what to check after

The Performance Wizard is Avada's guided tour of its own speed settings. According to the vendor's feature page it works through a fixed sequence, and each stage maps to settings you can later find by hand.

• Features: it scans the site and lets you disable features you do not use, which the vendor says reduces the markup loaded on each page.
• Icons: it finds which icons are used and where, so unused icon sets can stop loading.
• Fonts: it reviews the fonts the site loads and how they are served.
• Critical CSS: it lets you enable critical CSS generation, deferring styles a first view does not need.
• Media: it covers video facades, image quality, image sizes and the lazy-loading method.
• Compilation: it sets CSS and JavaScript compiling, asynchronous media-query files and non-render-blocking CSS.
• Recommendations: it scans assets and lists performance tips for the site.

Run it on a staging copy, accept its suggestions, then measure again. The Wizard is a sensible starting point, not a guarantee: it cannot see that the homepage slider is the slowest thing on the page, and it will not delete demo content. If the site has already gone sluggish over months rather than all at once, our Avada slow website repair guide covers the slow creep separately.

Global Options, Performance: the settings by name

Everything the Wizard touches lives in Avada Global Options under Performance, split into sections. These are the labels from ThemeFusion's speed documentation, with the vendor's warnings where it gives them.

Three more places finish the job. Advanced, Features turns off whole subsystems such as mega menus, the YouTube and Vimeo APIs and Google Maps scripts. Advanced, Post Types can disable the Avada Slider, Forms, Portfolio and FAQ post types. And under Builder Options, Avada Builder Elements, a Run Element Scan button finds elements nobody uses. Read the warning before disabling one: the docs say it removes that element from every page, old and new. Reset Avada Caches clears the compiled CSS and JavaScript when changes refuse to appear, and Avada CSS not updating covers the cases it does not fix.

Two sliders, a popup builder and a demo full of furniture

Avada's bundle is generous: Slider Revolution, LayerSlider, ACF Pro, Convert Plus, FileBird Pro and Avada Custom Branding arrive alongside the required Avada Core and Avada Builder. Generosity becomes weight the moment a plugin is activated and forgotten. Two slider plugins on one site usually means one slider in use and one loading its files for nothing, plus Avada's own slider post type as a third option.

Prebuilt websites add a second layer. The vendor lists 113 of them, and importing one brings pages, menus, forms, sliders, images and fonts chosen to show the theme off. Most owners rewrite the copy and keep the furniture. Months later the site still carries a portfolio nobody visits, a demo popup and images sized for a designer's monitor. When an import stopped halfway and left fragments behind, Avada demo import failed explains how to tidy up.

Tuning an Avada site without breaking it

Avada is three components that must stay in step: as of October 2026, Avada 7.16.2 expects Avada Core 5.16.2 and Avada Builder 3.16.2. Bring them into line before any speed work, or you will be measuring a version mismatch.

1. 1

   Update and back up

   Bring Avada, Avada Core and Avada Builder to matching versions on a staging copy. If the update itself fails, start with Avada update problems.

2. 2

   Measure four templates

   Test the homepage, a service page, a post and a shop or contact page on mobile in PageSpeed Insights. Record LCP, CLS and INP, plus field data where Google has it. Our PageSpeed Insights walkthrough explains which numbers matter.

3. 3

   Run the Performance Wizard

   Accept its feature, icon and font suggestions, enable critical CSS, and set compilation as it recommends. Measure again.

4. 4

   Settle who optimizes what

   If a caching plugin also combines or minifies CSS and JavaScript, switch those features off and keep it for page caching. Avada's compilers already merge files.

5. 5

   Clear out the bundle and the demo

   Deactivate unused bundled plugins, disable unused post types and features, run the element scan, and delete demo content you never adopted.

6. 6

   Replace the hero slider

   Swap any slider above the fold for one image, sized to its display width and uploaded as AVIF or WebP. A static hero paints sooner than any slider can.

7. 7

   Test the risky switches one at a time

   Try Load jQuery In Footer, jQuery Migrate off and Load Stylesheets In Footer separately. After each, check menus, forms and checkout on a real phone.

8. 8

   Rebuild critical CSS and clear caches

   Regenerate critical CSS, use Reset Avada Caches, purge the cache plugin and the server cache, then run the same four tests and write down the results.

How Avada's settings move LCP, CLS and INP

Largest Contentful Paint on an Avada page is usually the hero: a slider, a container background or a large image. Critical CSS and asynchronous media-query files get styles out of the way, and Preload Key Fonts helps when the hero is a headline. None of it helps if the hero image is several times larger than its container, a point Avada's own docs make about matching images to container sizes. The mechanism is laid out in WordPress vs Next.js on LCP, and slow LCP fixes for WordPress themes covers the theme side.

Cumulative Layout Shift has two Avada-specific sources. Font Face Rendering set to Swap All shows fallback text first, and the swap can move lines when the real font lands. Load Stylesheets In Footer, which the docs say can cause a flash of unstyled content, can also make content jump as styles arrive. Header Builder headers that shrink on scroll are the third suspect. See WordPress vs Next.js on CLS for the mechanism and Avada fonts not loading when fonts misbehave.

Interaction to Next Paint suffers from script volume and page size. Sliders, popups from Convert Plus, mega menus and third-party tags all compete for the main thread when a visitor taps. Optimize Offscreen Rendering reduces the rendering work below the fold, and disabling unused features removes markup. A mobile menu that responds slowly or not at all may be a script-order problem rather than a speed one; Avada mobile menu not working covers that. The INP comparison explains why less JavaScript is the only lasting cure.

What stays heavy however well you tune

• The builder's markup. Avada containers, columns and elements each write wrapper HTML. Disabling features trims it; it does not remove the model.
• The update cycle. After major updates the vendor tells you to rebuild critical CSS and clear Avada, plugin, browser and server caches. Skip that and a tuned site drifts.
• Server response time. The HTML has to arrive before any setting helps. Slow PHP or an overloaded host sits upstream of Avada.
• The Gzip option. Enable Gzip Compression works only on Apache servers with the right modules, per the docs. On other servers, compression is the host's job.
• Everything that is not Avada. Tag managers, chat, booking widgets and analytics run regardless of Global Options.

At that point the honest answer may be that the site is as fast as this stack gets. Our theme speed optimization service tests how far that is on staging before any promise, and the Avada repair hub lists the faults that tend to arrive with a slow site. Prefer someone to own the whole Avada build? See our Avada developers.

The point where Avada's speed work stops paying

For a single business site that is mostly a brochure, a tuned Avada build can be quick enough, and the one-time $69 license (as of October 2026) is hard to argue with. The math changes when speed is the business: a lead-generation site where mobile visitors call or leave, a site that publishes pages by city or service at scale, or a store where checkout delays cost orders. Then you are maintaining a settings panel, a bundle and three version numbers to hold onto a speed a coded site gets by construction.

A Next.js build ships only the code each page needs. Pages are prerendered and served from a CDN, next/image produces correctly sized images in modern formats, and next/font self-hosts fonts without a preload setting to choose. The trade is real: higher up-front cost, and layout changes go through a developer. Our Avada vs Next.js comparison sets the two side by side, and moving from Avada to Next.js explains how the content and every URL come across. Owners then edit in Athena CMS, where Argus flags slow pages before customers notice. Other themes are compared in the WordPress themes hub.