Skip to content
WordPress

Avada One 1.1: Lighter Pages, and What to Check Before You Update

Avada One 1.1 makes pages lighter and adds new tools, but it also renames CSS classes, stops loading jQuery on every page and switches icons to SVG. Here is what to test first.

Harsh PrajapatiFull stack developer
Published
Reading time
8 min

Avada One 1.1: Lighter Pages, and What to Check Before You Update

Avada One 1.1 was released on 20 November 2026, and it changes a lot about how Avada pages are built. Avada reports median reductions of around 60% in JavaScript, 40% in CSS and 20% in HTML tags, with new tools for fonts, tables, forms and emails. The catch is that it also renames CSS classes, stops loading jQuery on every page and switches icons to SVG, so custom code on your site can break. Update on a staging copy first, not straight on the live site.

This article is for business owners and agencies running Avada One sites: what changed, what can break and how to update safely.

What Avada One 1.1 is and who it affects

Avada One is the yearly subscription version of Avada. Avada Classic is a separate product, still sold on Envato with a lifetime licence. This update is for Avada One sites only. If you are not sure which one you have, our article on Avada One vs Avada Classic explains the difference, and Classic sites had their own update this week, covered in Avada Classic 7.17.

Avada's important update information page (opens in a new tab) lists 1.1.0 as the latest version, released on 20 November 2026, and says plainly that what can be affected by this update is your own custom code.

AreaWhat changed in 1.1Who notices
SpeedLess JavaScript, CSS and HTML, jQuery only where neededVisitors, especially on phones
IconsIcons load as inline SVG instead of an icon fontAnyone with icons added by hand
Class namesfusion- classes renamed to awb-Anyone with custom CSS
Content toolsFonts page, spreadsheet Table editor, new Accordion, native lightboxEditors
Marketing and salesEmails in every language, contact imports, Back In Stock, Birthday Emails, posts from formsMarketing teams and shop owners

What makes pages lighter

According to Avada's What's New page (opens in a new tab), the speed gains come from loading less code on each page.

Less JavaScript (median, Avada's figure)
60%
Less CSS (median, Avada's figure)
40%
Median mobile Lighthouse score of Avada's prebuilt home pages
86 to 96
  • Less CSS per page. Avada says around 40% less CSS is loaded per page.
  • jQuery only where needed. Avada puts JavaScript at around 60% less, and up to 88% less with jQuery loaded only where it is needed. Twelve older scripts are gone, including iLightbox, Modernizr and several jQuery add-ons.
  • Fewer HTML elements. Avada puts the drop at around 20% fewer HTML tags (median), and its update notes say Text Block, Image, Button and Title elements now output less HTML.
  • Inline SVG icons. Icons are now inline SVG instead of an icon font, and only the icons a page uses are loaded. Avada says this saves 20 to 45 KB per page, and up to 185 KB where Font Awesome was used.

Avada's Lighthouse figure comes from its own prebuilt home pages, measured with mobile Lighthouse, the same engine as Google PageSpeed Insights, and Avada notes that scores move a few points between runs. The percentages are Avada's medians. They show the direction, not a promise for your site. A site slowed down by large images, heavy plugins or slow hosting will still need those fixed. Our Core Web Vitals guide explains what Google's Core Web Vitals measure and what affects them.

New tools for editors and marketing

Beyond speed, 1.1 adds a long list of features. The ones business sites are most likely to use:

  • Fonts page. Fonts are now managed on one Fonts page, and Google variable fonts load as one file.
  • Native lightbox. Avada's own lightbox, with zoom and custom colours, replaces iLightbox.
  • Spreadsheet-style Table editor. Paste straight from Excel or Google Sheets.
  • Accordion element. Replaces Toggles, with better accessibility.
  • Color Mode Condition and Image Preloading. A new display condition based on colour mode, and preloading for key images.
  • Emails in every language. Send emails in several languages, with AI translation included.
  • Contact imports. Bring contacts and emails in from Mailchimp, MailPoet, FluentCRM and others.
  • Posts from forms. A Create Post action and a Rich Text field turn form submissions into posts.
  • Back In Stock and Birthday Emails. Back In Stock alerts for shop customers, plus birthday emails.
  • Connect Avada Sites. Link several Avada sites together.

Some of these take over as soon as you update: the native lightbox replaces iLightbox and fonts move to the new Fonts page, so check galleries and fonts on staging. The rest are tools to use when you are ready.

What can break when you update

This is the part to read before clicking update. Avada's important update information page lists these changes.

ChangeWhat can breakWhat to do
fusion- classes renamed to awb-Custom CSS that targets old class names, including numbered ones like fusion-builder-row-3Install the Avada Migration plugin 1.1 and run its Custom CSS tool after updating. It does not check CSS in a child theme or another plugin
jQuery no longer loads on every pageCustom scripts that use jQuery or $, which show "jQuery is not defined" in the browser consoleTurn on Load jQuery On Every Page in Global Options, Performance, or load jQuery as a dependency
Icons now SVG, icon font not loadedIcons typed as HTML, such as an i tag with fa classes, show blank. Icons styled with the icon font need restylingAvada says icon styles set with ::before need restyling. Replace hand-coded icons and check them on staging
Leaner markupCSS written for the old structure, such as a rule for paragraphs inside an elementReview the Markup Mode setting (Automatic or Atom) and adjust the custom CSS
Responsive typography script removedLarge headings may stay large on phonesRun the Responsive Typography tool in the Avada Migration plugin
Paragraph spacing now applies to every paragraphSpacing can look differentThe update adds a commented rule to your custom CSS that keeps the old spacing. Check it on staging
Scripts rewritten, new lightboxCustom code that calls old functions or the old lightboxTest menus, sticky headers, tabs, sliders, forms, modals, Off Canvas, lightbox and shop pages

Two smaller points: Font Awesome Pro Light and Duotone icons show as the closest free style unless you upload your Pro set, and if you plan to import a prebuilt website or Studio content, Avada says to update to 1.1 first. Avada's 1.1 change list also includes compatibility with WooCommerce 11.3.

How to update safely

  1. Full backup
  2. Staging copy
  3. Update and run Migration tools
  4. Test key pages
  5. Clear caches
  6. Update live
  1. Take a full backup of the database and the wp-content folder, and ideally wp-config.php and .htaccess too. Make sure you know how to restore it.
  2. Update a staging copy first. Avada itself recommends a staging site for major releases.
  3. Update the theme the right way. If you update by hand, replace the whole Avada folder. Do not rename it or keep an old copy in the themes folder.
  4. Install the Avada Migration plugin 1.1 and run its Custom CSS and Responsive Typography tools, after the update, not before.
  5. Open the browser console on key pages and look for "jQuery is not defined". If you see it, switch on Load jQuery On Every Page while the scripts are fixed.
  6. Test what earns money on desktop, tablet and phone: home page, menus, contact and quote forms, popups, galleries and checkout if you sell online.
  7. Clear every cache. Click Reset Avada Caches, then clear any caching plugin, server cache, CDN and browser cache, and regenerate Critical CSS if you use it.
  8. Then update the live site, at a quiet hour, and repeat the quick checks.

A child theme stays active through the update, but template files or custom PHP copied into it may be out of date, so check those too.

Should you update now or wait?

Update, but not in a rush. Avada's update notes for 1.1 do not mention a security fix, so unlike a security release there is no reason to skip testing. The speed gains are worth having once your custom code has been checked.

Your situationWhat we suggest
Simple site, no custom code, good backupUpdate on staging, check key pages, then update live
Custom CSS, scripts or a child themeStaging test with the Migration tools, fix what breaks, then update
WooCommerce shop in Black Friday weekWait until after Cyber Monday on 30 November unless a security fix appears
Nobody knows what custom code the site hasGet a developer to test it on staging first

If you want the update tested and the custom code fixed for you, our Avada website development service covers it. To turn Avada's lighter pages into better real-world speed scores, website performance optimisation looks at images, plugins and hosting too. And if nobody is looking after updates at all, website maintenance and support keeps the theme, plugins and backups current.

Frequently asked questions

When was Avada One 1.1 released?

Avada One 1.1.0 was released on 20 November 2026, according to Avada's important update information page.

Does Avada One 1.1 apply to Avada Classic sites?

No. Avada One and Avada Classic are separate products. Classic sites got Avada 7.17 on 17 November 2026, which shares some features, such as the native lightbox and the spreadsheet-style table editor.

Why does my site show "jQuery is not defined" after the update?

Avada One 1.1 no longer loads jQuery on every page, so a custom script that expects it fails. Turn on Load jQuery On Every Page under Global Options, Performance, as a quick fix, then have the script updated to load jQuery properly.

Will Avada One 1.1 make my site faster?

It should make pages lighter, because they load less JavaScript, CSS and HTML. Avada's own prebuilt home pages went from a median mobile Lighthouse score of 86 to 96. Your result depends on your images, plugins and hosting, so measure your own pages before and after.

Sources

The facts in this article were checked against these pages, last reviewed 21 November 2026.

  1. Important Update Information, Avada Documentationavada.com/documentation/important-update-information/
  2. What's New in Avada One, Avadaavada.com/whats-new/
  3. Avada Changelog, Avada Documentationavada.com/documentation/avada-changelog/
  4. Avada Pricing, Avadaavada.com/pricing/
Harsh Prajapati, the author

Written by

Harsh Prajapati

Freelance full stack developer, founder of Worklancio

Web developer since 2018, freelancing since 2022. Builds WordPress sites and plugins, web apps and CRMs from Ahmedabad.

You may also like