Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Guide

How to Speed Up an Elementor Site

Short answer

To speed up an Elementor site, turn on Optimized DOM Output, Improved Asset Loading and Optimize Control Loading under Elementor → Settings → Features. Set the CSS print method to External File, rebuild old sections as containers, and remove add-on plugins you do not use. Then add a page cache and re-run the same speed test to confirm the gain.

Key takeaways

  • Elementor 3.15 made Optimized DOM Output and Improved Asset Loading stable features that are active by default.
  • Elementor 3.21 added Optimize Control Loading and reworked lazy loading for background images.
  • Setting the CSS print method to External File lets browsers cache page CSS instead of re-reading it in every page.
  • Containers use flexbox layout and produce less markup than old sections and columns.
  • WordPress lazy-loads images by default since 5.5, but the hero image should never be lazy-loaded.

What makes an Elementor site slow?

An Elementor site slows down when pages carry extra CSS, JavaScript, fonts and images that the visitor never needs.

Elementor describes itself as the website builder powering more than 24 million websites worldwide, according to its WordPress.org plugin page. Each widget on a page can add its own files, so a page built from many widgets can load far more code than the visitor sees.

The builder is not the only cause. Hosting, image sizes, add-on plugins and missing page caching all add up on the same page. Fix the Elementor settings first, then check the rest.

See also our guide on how to speed up Elementor for the shorter version of the same fixes.

What do you need before you start?

You need an admin login, a backup, and a speed reading from before you change anything.

  • A full backup of files and database, so you can undo a setting that breaks a layout.
  • A speed reading for your slowest page, taken before and after the changes, so you can compare like with like.
  • A low-traffic hour or a staging copy, since some settings change how pages look.
  • Elementor 4 is the current version as of November 2026, according to the plugin page on WordPress.org.

Allow 30 to 60 minutes for the settings below, plus extra time if you rebuild heavy pages as containers.

Which Elementor features should you turn on?

Turn on Optimized DOM Output, Improved Asset Loading and Optimize Control Loading under Elementor → Settings → Features.

FeatureWhat it doesSince
Optimized DOM OutputRemoves extra wrapper elements from Elementor HTMLStable in 3.15
Improved Asset LoadingLoads widget CSS and JavaScript only where the widget is usedStable in 3.15
Optimize Control LoadingChanges how widgets render to cut time to first byte3.21
Lazy Load Background ImagesLoads below-the-fold background images laterReworked in 3.21

Elementor 3.15 made Optimized DOM Output and Improved Asset Loading stable features that are active by default on all websites, according to Elementor's 3.15 release post. If your site was built before that version, check that both are active.

Elementor says its 3.21 Optimize Control Loading cuts time to first byte by 20 to 30 percent, according to the Elementor 3.21 release post. That is the vendor's own figure, so treat it as a direction, not a promise for your site.

The old Experiments tab was renamed Features in Elementor 3.11, per the Elementor developers update. Older tutorials that point you to Experiments mean the same screen.

Our Elementor performance settings guide explains each switch in more detail.

How do you set the CSS print method?

Go to Elementor → Settings → Performance and set CSS Print Method to External File.

External File writes the page CSS to files the browser can cache, instead of printing the same CSS inside every page. That keeps the HTML smaller and lets repeat visits reuse the cached file.

Then open Elementor → Tools and regenerate the CSS files, so every page picks up the new setting. Clear your page cache as well, or you will keep seeing the old pages while you check the result.

Should you rebuild sections as containers?

Yes, where you can, since containers use flexbox layout and produce less markup than old sections and columns.

The Flexbox Container feature was promoted to release candidate status in Elementor 3.11, according to the Elementor developers update. Build new pages with containers, and start converting the slowest old pages first.

Avoid nesting sections inside sections. Each nested layer adds wrapper elements to the page, and those wrappers add up across a long page. One container with a few widgets inside it beats three nested sections doing the same job.

How do you cut unused widgets and add-ons?

Remove add-on plugins you do not use, and switch off widgets your pages never show.

Elementor's free version ships with more than 40 widgets, according to its WordPress.org plugin page, and Pro adds more than 100. Every active add-on can add its own CSS and JavaScript to pages that never use it.

  • Open Dashboard → Plugins and list every Elementor add-on. If you cannot name a page that uses it, deactivate it and check the site.
  • Remove duplicate tools. Two slider plugins, two form plugins or three icon packs all load their own files.
  • Keep one tool per job. A single well-kept add-on beats three overlapping ones.
  • Check the Features screen for widget controls, and remove any add-on that exists only to add one widget you never use.

Deactivate one add-on at a time and reload a page that used it. If the page still looks right, leave the add-on off.

How do you speed up images and fonts?

Serve images at the size they display, in a modern format, and load only the fonts you use.

WordPress lazy-loads images by default since version 5.5, according to the Make WordPress Core lazy-loading tag page. In each Elementor image widget, pick the registered image size that matches the display size, so the browser does not download a 4,000-pixel file for a 600-pixel slot.

Never lazy-load the hero image. WordPress 5.9 skips the first content image or iframe from lazy loading by default, according to the same Make WordPress Core page, but a page-builder hero can still be marked lazy by the builder, so check the hero widget yourself.

Largest Contentful Paint is usually the hero image. Our guide on how to pass Core Web Vitals in WordPress explains how to check that metric on your own pages.

For fonts, use system fonts where you can, and load only the weights you use. A font family with six weights loads six files, even if the page only shows two of them.

How do you handle background images and video?

Lazy-load background images below the fold, and lazy-load video embeds instead of loading the player on page open.

Elementor 3.21 reworked lazy loading for background images so above-the-fold images load first and the rest load later, according to the Elementor 3.21 release post. Turn it on under Elementor → Settings → Features.

A YouTube embed loads the player as soon as the page opens, even if nobody watches. Web.dev's iframe lazy-loading article says lazy-loading YouTube embeds saves around 500 KB on the first page load, and that Chrome.com cut time to interactive by 10 seconds by lazy-loading offscreen YouTube embeds.

Lazy-load YouTube embeds in WordPress with the loading attribute or a facade plugin that shows a thumbnail until someone presses play.

Do you still need a caching plugin?

Yes, because Elementor's settings cut unused code but do not cache pages, so you still need a page cache.

Pair the Elementor settings with a caching plugin and a host that fits the site. Our guide to speeding up WordPress walks through the caching layer and the other layers that sit around it.

A lighter theme helps too. Our theme speed comparison compares three light themes on speed, if the theme is also on your list to change.

How do you check that it worked?

Re-run the same speed test on the same page and compare the before and after readings.

Test the same page, on the same connection, after clearing the cache. Look at Largest Contentful Paint and total page weight first, since those move most when unused code and images drop away.

If a page looks broken after a change, switch that feature off and clear the cache. Elementor's 3.15 release post warns that Optimized DOM Output may affect websites still running on Elementor 3.0 or earlier, so older sites deserve a careful check after each switch.

What mistakes should you avoid?

The main mistakes are changing every setting at once, lazy-loading the hero image, and skipping the backup.

  • Change one feature at a time and check the page. If you change five things and the layout breaks, you will not know which one did it.
  • Do not lazy-load the hero image or the first image on the page. That delays the largest visible element.
  • Do not keep five add-ons that do the same job. Each one adds files to pages that never use it.
  • Do not judge speed from one test run. Test twice, after clearing the cache, and compare the same page.
  • Do not forget to regenerate CSS after changing the print method. Old CSS files will keep the old setting in place.

Frequently asked questions

Do I need Elementor Pro to speed up my site?

No. The free version includes the performance features covered in this guide, such as Optimized DOM Output and Improved Asset Loading. Pro adds more widgets and builders, but speed work starts with the free settings, images and caching rather than with a purchase.

Should I convert all my sections to containers?

Containers use flexbox layout and produce less markup than the old sections and columns. Build new pages with containers, and convert the slowest old pages first. Converting every page at once takes time, so work through the busiest pages in order.

What should I do if a page looks broken after enabling a feature?

First switch the feature back off and clear the cache. Change one feature at a time, so you always know which switch caused the problem. Elementor warns that Optimized DOM Output can affect sites still running Elementor 3.0 or earlier.

Can add-on plugins slow down an Elementor site?

Yes, if you run more than one plugin that does the same job, such as two slider plugins or three icon packs. Each active add-on can load its own CSS and JavaScript on pages that never use it, so removing the extras is one of the fastest wins.

Do I still need a caching plugin with Elementor?

Yes. Elementor's settings cut unused code, but they do not store finished pages, so you still need a page cache plugin or host caching. Use both: Elementor trims the code, and the cache skips building the page on repeat visits.

Sources

  1. Elementor 3.15 is Here Elementor
  2. Introducing Elementor 3.21: Performance Improvements Elementor
  3. Elementor 3.11 Developers Update Elementor Developers
  4. Elementor Website Builder WordPress.org
  5. It's time to lazy-load offscreen iframes! web.dev
  6. Lazy-loading images and iframes Make WordPress Core

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test