Plugin how-tos · Guide
What Are Elementor's Performance Settings and How Do You Use Them?
Short answer
Elementor's performance settings are switches in the Performance and Features tabs that cut page weight and speed up loading. The most useful ones are Optimized Image Loading, Lazy Load Background Images, Element Caching and Load Google Fonts Locally. Turn them on one at a time, then check the result in PageSpeed Insights.
Key takeaways
- Optimized Image Loading marks your largest visible image as high priority and lazy-loads images below the fold.
- Element Caching stores a widget's rendered HTML in the database, but it must only be used on static elements.
- Since Elementor 3.32.1, Load Google Fonts Locally defaults to Disabled and must be turned on again after updating.
- Elementor's Image Optimization tool resizes large images to 1920 pixels by default and can convert JPEGs to WebP.
- A good Largest Contentful Paint is 2.5 seconds or less, measured across real visits to your pages.
Where do you find Elementor's performance settings?
You find them in the WordPress admin under Elementor > Editor > Settings, split between the Performance tab and the Features tab.
Elementor moved its admin menu in January 2026, so older guides that point to Elementor > Settings now lead to the Editor submenu instead. Elementor's own help page on the new menu was last updated on January 28, 2026. The Performance tab holds the stable settings, and the Features tab holds experiments and newer features.
Elementor's help page Improve performance features was last updated on June 19, 2026, and it lists every setting in one place. Use it as your map before you change anything.
What you need before you start
- Admin access to the WordPress dashboard.
- Elementor installed and active. The WordPress.org plugin page lists 10+ million active installations and requires WordPress 6.8 or higher and PHP 7.4 or higher, as of November 2026.
- A backup or a staging copy, so you can undo a change that breaks a layout.
- About 30 minutes, plus time to re-check your pages after each change.
What does Optimized Image Loading do?
Optimized Image Loading marks your largest visible image as high priority and lazy-loads the images below the fold.
The setting applies fetchpriority="high" to the Largest Contentful Paint (LCP) image and loading="lazy" to images further down the page, according to Elementor's performance features help page. LCP is the time it takes for the largest visible image or text block to appear, and a good LCP is 2.5 seconds or less.
Elementor's developers update for version 3.17 says this feature improved LCP by 5 to 10 percent, depending on how complex the page is. The same update says the feature scans each breakpoint, finds the largest asset, and raises its priority.
It was upgraded from beta to a stable feature in Elementor 3.19, per the Elementor 3.19 developers update.
To turn it on, go to Elementor > Editor > Settings, open the Performance tab, find Optimized Image Loading, and pick Enable from the dropdown. Then save your changes.
How does Lazy Load Background Images work?
Lazy Load Background Images delays every background image except the first one until the visitor scrolls near it.
Background images sit inside sections and containers, so the browser cannot lazy-load them the way it lazy-loads a normal image tag. This setting handles that gap. The first background image still loads at once, which keeps your hero section fast, while the rest wait their turn.
Turn it on in the same place: Elementor > Editor > Settings, then the Performance tab, then pick Enable next to Lazy Load Background Images. If your hero uses a background image, check that it still appears at once after you save.
What is Element Caching and when should you use it?
Element Caching stores a widget's rendered HTML in the database, so the next visit reads that copy instead of building the widget again.
When widgets render on the server, Elementor saves the HTML output in the database. The next time the element appears, it is drawn from the database instead of being rendered fresh.
Elementor's help page says this cuts server memory use and reduces Time To First Byte (TTFB) for visitors. You can read the full steps in Elementor's Element Caching help page.
The feature is inactive by default, and you should only use it on static elements. It cannot be used on elements that show dynamic tags, shortcodes, or content that changes per visitor.
One example is a widget that shows the visitor's name. Turning caching on for a dynamic widget can show one visitor's content to another.
Six layout elements are cached by default and you cannot change their status: Container, Grid Container, Off Canvas, Section, Column, and Inner Section.
How to turn on caching for one widget
- Open the page in the Elementor editor and click the widget.
- Click the Advanced tab in the side panel.
- Find Cache Settings and pick Active from the dropdown.
- Update the page and check that it still shows the right content.
How to set cache expiry for the whole site
- In the WordPress admin, go to Elementor > Editor > Settings.
- Click the Performance tab.
- Find Element Cache Expiration and pick how often the cache clears.
- Save your changes.
Clearing the cache happens at site level, so every cached element refreshes on the same schedule. Pick a shorter interval for pages that change often, such as news or sale pages.
How do you load Google Fonts locally?
You turn on Load Google Fonts Locally, and Elementor downloads the fonts your pages use and serves them from your own server.
Each font family and weight is a separate file the browser must download. Loading them from Google's servers adds extra requests and a connection to another domain.
Serving them from your own server removes those requests. Elementor introduced the feature in version 3.27 and merged it into the plugin in version 3.30, according to the Elementor 3.27 developers update.
One detail catches many people out. Starting with Elementor 3.32.1, the setting became optional and its default switched to Disabled.
Elementor's help page says that if you enabled it in an earlier version, you must enable it again after updating. The help page was updated on January 20, 2026.
Steps to turn it on
- In the WordPress admin, go to Elementor > Editor > Settings.
- Click the Performance tab.
- Scroll to Load Google Fonts Locally and pick Enable.
- Save your changes, then open a page that uses a Google Font.
- Check that the font files now sit in the
/wp-content/uploads/elementor/fonts/folder on your server.
If you use custom fonts instead of Google Fonts, Elementor Pro lets you upload them yourself. The Elementor Free vs Pro guide explains which font features need the paid version.
What does the Google Fonts Load setting do?
The Google Fonts Load setting controls what visitors see while a Google Font is still downloading, and Swap shows fallback text at once.
Without this setting, the browser may hide text until the font arrives, which leaves a blank space where your heading should be.
Swap tells the browser to show the text in a system font first, then switch to the Google Font once it loads. Elementor's typography guide describes Swap as displaying text with a lighter, faster-loading system font while the desired font loads.
To change it, go to Elementor > Settings > Advanced and open the Google Fonts Load dropdown. Pick Swap for the fastest visible text. Elementor's developer docs note that the same choice can be set through the font-display hook for developers who need finer control.
Keep your font list short as well. Two families with two weights each means four font files, and every extra weight adds another download. Drop weights you never use in your design.
What are Inline Font Icons?
Inline Font Icons render your icons as inline SVG instead of loading the Font Awesome and eicons font files.
Icon fonts load a whole font file even when a page uses only two or three icons. Inline SVG sends only the icons that page uses.
Elementor lists Inline Font Icons as a stable feature in the Features tab. Its help page says it skips the Font Awesome and eicons libraries and their related CSS files and fonts.
To turn it on, go to Elementor > Editor > Settings, open the Features tab, find Inline Font Icons, and pick Active. Then open a page with icons and check that every icon still shows. Old custom CSS aimed at the icon font files may need a check, since those files no longer load.
What does Optimized Gutenberg Loading do?
Optimized Gutenberg Loading removes block editor scripts and styles that your Elementor pages do not use.
Many WordPress sites load block editor files on every page, even pages built fully with Elementor. This stable setting in the Performance tab dequeues the unused files, so the browser downloads less on each visit. Turn it on the same way as the other Performance tab settings: pick Enable and save.
Check any page that mixes blocks and Elementor content after you enable it. If a block looks broken, turn the setting off and report the clash to your host or developer. Pages built only with Elementor should see no change in how they look.
How do you set up Elementor Image Optimization?
You open Elementor > Image Optimization > Settings, pick a compression level, and then run bulk optimization on the images already in your library.
Image Optimization is a separate plugin from Elementor, and it compresses images as you upload them. Its settings page shows how much space you saved and how many images you have optimized. The Image Optimization settings help page was last updated on September 25, 2026.
| Setting | Default | What it does |
|---|---|---|
| Compression level | Lossless or Lossy, your choice | Lossless keeps the original quality with smaller savings, while Lossy cuts more size and lowers quality a little |
| Optimize new uploads | On | Compresses each image as it enters the media library |
| Resize larger images | On, 1920 pixels | Shrinks images larger than 1920 pixels wide or tall |
| Clear EXIF metadata | On | Strips extra camera data from the file |
| Backup Original Images | On | Keeps a copy of the original so you can restore it |
| WebP conversion | Off until you turn it on | Turns optimized JPEGs into WebP files |
Elementor's help page gives one worked example: a 1.16 MB image saved 56 percent with the default settings. Your own savings will differ, since they depend on the image and the compression level you pick.
A content delivery network can speed up image delivery further. The Cloudflare Free vs Pro for WordPress guide compares the free and paid tiers.
How do you check whether the settings helped?
You run the same page through PageSpeed Insights before and after each change, and you compare the Largest Contentful Paint result.
PageSpeed Insights is Google's free tool for checking a page on mobile and desktop. Its documentation says it combines lab data from Lighthouse with field data from the Chrome User Experience Report.
That field data covers the previous 28 days of real visits. The mix matters, because lab results show one simulated visit while field data shows what real visitors felt.
Follow these steps for a fair comparison:
- Run PageSpeed Insights on the page before you change anything and save the LCP number.
- Turn on one setting, clear every cache, and run the same page again.
- Compare the LCP number and the list of issues, not just the headline score.
- Wait for field data to update before you judge a change, since it covers 28 days.
A good LCP is 2.5 seconds or less. A result between 2.5 and 4 seconds needs improvement, and anything over 4 seconds is poor.
If you want a wider speed plan beyond Elementor, the guide to speeding up WordPress covers hosting, caching, and images together.
For the responsiveness metric, see what INP means.
What mistakes should you avoid?
Turning on every setting at once is the most common mistake, because you cannot tell which change helped or hurt.
Change one setting, save, clear the cache, and check the page. Then move to the next one. That order takes longer, but it gives you a clear record of what each switch did.
Other mistakes to avoid:
- Turning on Element Caching for a widget that shows dynamic content, such as a name, a price, or a shortcode result.
- Lazy-loading your hero image or first background image, which delays the largest visible element.
- Forgetting to re-enable Load Google Fonts Locally after updating past version 3.32.1, when the default changed to Disabled.
- Skipping the cache clear after a change, then judging the old cached page instead of the new one.
- Adding a caching plugin on top of Elementor's own caching without checking for clashes first. The WP Rocket vs LiteSpeed Cache comparison can help you pick one caching tool and stick with it.
Frequently asked questions
Do Elementor performance settings work on the free version?
Yes, most of them do. Optimized Image Loading, Lazy Load Background Images, Optimized Gutenberg Loading, Inline Font Icons and Element Caching are in the free plugin. Load Google Fonts Locally is also free. Custom fonts and the Image Optimization plugin have their own rules, so check which plan covers them before you rely on them.
Will turning on Element Caching break my forms or dynamic content?
It can, if you cache the wrong widget. Element Caching must only be used on static elements, and it cannot be used on elements with dynamic tags or shortcodes. A form that shows a visitor's name or a price that changes per visitor should stay uncached. If content looks stale or wrong after enabling it, turn caching off for that widget.
Should I lazy-load my hero image?
No. The hero image is usually the largest visible element, so delaying it makes your Largest Contentful Paint slower. Optimized Image Loading already marks that image as high priority and lazy-loads only the images below the fold. Keep the hero loading normally and let the setting handle the rest of the page.
Why did Load Google Fonts Locally turn itself off?
It did not turn itself off by accident. Starting with Elementor 3.32.1, the feature became optional and its default changed to Disabled. Anyone who enabled it in an earlier version must enable it again after updating. Go to Elementor, then Editor, then Settings, open the Performance tab and pick Enable.
How long does it take to see results in PageSpeed Insights?
Lab results change as soon as you re-run the check, because Lighthouse audits the live page. Field data takes longer, since it covers the previous 28 days of real visits. Judge a change by the lab result first, then watch the field data over the next few weeks to confirm real visitors felt the gain.
Sources
- Improve performance features Elementor
- Speed up page loading with Element Caching Elementor
- Elementor and Google fonts Elementor
- Explore the Image Optimization Settings Elementor
- Elementor 3.17 Developers Update Elementor Developers
- About PageSpeed Insights Google for Developers
- Elementor Website Builder WordPress.org
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.
Thanks — we review requests within 3 business days.
