Which Elementor Performance Settings to Turn On, and Which to Skip

Elementor has built-in options that make pages lighter. The ones I turn on, the ones I test carefully, and how to do it safely.
Elementor performance settings: two computer monitors sitting on top of a wooden desk

Elementor ships with several built-in options that make pages lighter, but they’re spread across different screens, their names change between versions, and some can break a layout if switched on blindly. I’ll walk you through the Elementor performance settings I check on every site I work on, what each one does in plain English, and how to turn them on without surprises. It assumes a reasonably recent version of Elementor and Elementor Pro.

Where to find the settings

Most options live under Elementor > Settings, split across a Performance tab and a Features tab. Older versions put some of them on an Experiments screen instead. Elementor regularly promotes options from experiment to default, so if you can’t find a setting mentioned here, it has probably become standard and is already on.

Before changing anything:

  1. Work on a staging copy, or at least take a full backup.
  2. Run PageSpeed Insights on three or four key pages and save the results.
  3. Change one setting at a time, then clear all caches and regenerate Elementor’s files under Elementor > Tools.

The Elementor performance settings I turn on

CSS print method: external file

Elementor can either write each page’s styles into a separate CSS file or embed them in the page. External files can be cached by the browser and the CDN, so I use that option on almost every site. Internal embedding can help in rare setups where the CSS file loads slowly, but it makes every page heavier.

Improved asset loading

Older versions of Elementor loaded the scripts for every widget on every page. This feature loads widget scripts only on pages that actually use those widgets. It’s low risk and usually a clear win.

Improved CSS loading

The same idea for styles: widget CSS loads only where it is needed, instead of one large stylesheet for everything.

Inline font icons

Instead of loading the whole Font Awesome icon font to show four icons, Elementor renders them as small inline SVGs. That means fewer requests and no flash of missing icons. Also switch off Font Awesome 4 support if your site does not use old icon code, because it loads an extra compatibility file.

Google Fonts: load locally and swap

Set Google Fonts to use swap, so text shows immediately in a fallback font, and turn on local loading so the font files come from your own server instead of Google’s. That removes extra connections and helps with privacy rules in Europe.

Lazy load background images

Background images on sections further down the page load only when the visitor scrolls near them. Leave the hero alone, though. It should load right away.

Flexbox Containers

Containers replace the old section and column structure with far fewer wrapper elements. On new builds I use them exclusively. On existing sites, turning the feature on doesn’t convert old pages, so plan the conversion as a separate job.

Lazy load and image overlay on video widgets

This one is a widget setting rather than a site setting, but it matters. Elementor’s Video widget can lazy load YouTube and Vimeo embeds and show an image overlay instead of the full player. With both on, the heavy player only loads when someone presses play. On a page with two or three embedded videos, the difference is large.

Settings to test carefully

  • Element caching. Stores the rendered output of widgets so they don’t have to be rebuilt on every request. It helps on uncached pages, but dynamic widgets, anything showing the logged-in user, cart contents or randomized content, need caching turned off for that element.
  • Optimized image loading. Newer versions can manage lazy loading and fetch priority for images. Check that it doesn’t conflict with a caching plugin doing the same job, and that your hero image is still not lazy loaded.
  • Local fonts in two places. If your caching plugin also hosts Google Fonts locally, pick one tool for the job, not two.
  • Additional custom breakpoints. Extra breakpoints such as laptop, widescreen or mobile extra give you more layout control, but each one adds CSS to every page. Only add the ones your design really needs.

When I roll these out on a client site, I keep a short written log: the setting, the date, the before and after numbers, and anything that looked different. If something odd turns up a week later, the log tells you exactly which change to undo, instead of guessing between six.

What the settings cannot fix

These options trim Elementor’s own overhead. They do not fix a 3 MB hero image, a dozen third-party scripts, slow hosting or a page built with duplicate desktop and mobile sections. They also do nothing about the addon packs installed alongside Elementor. Use Elementor’s Element Manager screen to see which widgets are actually used and deactivate the rest, and do the same in any addon plugin that offers it.

In practice the settings give you a cleaner baseline. The big gains still come from images, caching, scripts and page structure, which is what my WordPress speed optimization work focuses on. If a setting change breaks something on a live site and you need it fixed quickly, that falls under WordPress error fixes.

The short version

  • Back up or use staging, and save baseline PageSpeed results.
  • Set the CSS print method to external file.
  • Turn on improved asset loading and improved CSS loading.
  • Turn on inline font icons and turn off Font Awesome 4 support if unused.
  • Set Google Fonts to swap and load them locally.
  • Enable lazy loading for background images, but keep the hero eager.
  • Deactivate unused widgets in the Element Manager.
  • Regenerate Elementor files and clear every cache after each change.

Worth reading next: why Elementor excessive DOM size happens and how to fix it and how to choose WordPress hosting for speed without guesswork.

Common questions

Why can’t I find a setting mentioned in a tutorial?

Elementor moves and renames options between versions, and many experiments become permanent defaults. If it’s missing, check the Features tab and the changelog. It’s often already on.

Can these settings break my site?

Occasionally, especially on older sites with custom code or third-party addons. That’s why I change one setting at a time on staging and check forms, menus and popups after each one.

Do I still need a caching plugin?

Yes. Elementor’s settings reduce what each page loads. Page caching makes the server deliver it quickly. They solve different problems.

Will these settings get my site a perfect score?

No, and a perfect score is not the goal. Passing Core Web Vitals for real visitors is.

If you want a second pair of eyes on your Elementor setup, request a free website review and I’ll tell you which settings and changes will make the biggest difference.

Share this article

Shehzad Akram

About the author

Shehzad Akram

Senior WordPress and Shopify developer in Lahore, Pakistan, Top Rated on Upwork with 100% Job Success. I write these notes from real client work: what broke, what fixed it, and what I check every time.

Keep reading

More notes from real client work