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

Plugin how-tos · Guide

How to Speed Up Elementor

Short answer

To speed up Elementor, turn on its built-in performance features, cut the number of widgets and large images on each page, and add page caching. Check your PHP version and memory limit first, because a slow server limits every other fix. Measure the page before and after each change with PageSpeed Insights.

Key takeaways

  • Elementor needs WordPress 6.8 or newer, PHP 7.4 or newer, and 256 MB of WordPress memory as of November 2026.
  • Element Caching, introduced in Elementor 3.22, is now on by default and serves cached widget output instead of re-rendering it.
  • A good Largest Contentful Paint is 2.5 seconds or less at the 75th percentile of page loads, according to web.dev.
  • Every widget, image, font, and animation on a page adds work, so removing what visitors do not need is often the fastest fix.
  • Regenerate Elementor files under Elementor > Tools after changing settings, so old CSS does not hide the result.

How do you speed up Elementor in the shortest time?

Turn on Elementor's built-in performance features, remove heavy widgets and large images, then add page caching.

Start with the settings that cost nothing and need no code. Open “Elementor > Settings > Features” and turn on the performance features listed there, including Optimized Markup and Element Caching if they are not already active.

Next, look at your slowest page, not your whole site. One heavy home page or landing page usually causes most of the complaints, so fix that page first and use it as your test case.

Then add page caching if your host does not already cache pages for you. Caching stores a finished copy of a page, so the server does not rebuild it for every visitor.

What should you measure before you change anything?

Measure your slowest page in PageSpeed Insights before you change a setting.

PageSpeed Insights shows field data from real Chrome users when a page has enough traffic, plus lab results for a single simulated load. Save the numbers for Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift before you start.

Google's good thresholds, published on web.dev, are clear targets: Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, each at the 75th percentile of page loads (https://web.dev/articles/defining-core-web-vitals-thresholds).

Largest Contentful Paint, or LCP, is the render time of the largest image, text block, or video visible in the viewport. A good LCP is 2.5 seconds or less at the 75th percentile, split by mobile and desktop, according to web.dev (https://web.dev/articles/lcp).

Also note which element PageSpeed Insights names as the LCP element. If it names a hero image, fix the image first. If it names a heading, the delay is more likely in the server response or in render-blocking CSS.

Which Elementor settings help speed the most?

Turn on Optimized Markup, Element Caching, and local Google Fonts first, because they cut work on every page.

Optimized Markup removes unneeded HTML tags from elements and widgets, which shrinks the DOM size. Elementor introduced it in version 3.25, improved it in 3.26 and 3.27, and marked it stable in version 3.31 (https://developers.elementor.com/elementor-3-31-developers-update/).

Element Caching serves a cached copy of a widget instead of rendering it on every page load. Elementor introduced it in version 3.22, and its 3.31 update notes say it is now enabled by default on all websites (https://developers.elementor.com/elementor-3-31-developers-update/).

Elementor's developer docs say Element Caching reduces server memory usage by 99% and improves Time to First Byte, or TTFB, on the front end (https://developers.elementor.com/docs/widgets/widget-output-caching). That figure is Elementor's own claim for cached widget output, not a result measured for your site.

SettingWhere to find itWhat it does
Optimized MarkupElementor > Settings > FeaturesRemoves unneeded HTML tags and shrinks the DOM
Element CachingElementor > Settings > FeaturesServes cached widget output instead of re-rendering it
Load Google Fonts LocallyElementor > Settings > FeaturesServes Google Fonts from your own server
Improved Asset LoadingElementor > Settings > FeaturesLoads scripts and styles only where they are used

Load Google Fonts Locally downloads the Google Fonts used on Elementor pages to your server, at “/wp-content/uploads/elementor/fonts/”, and updates the generated CSS to use those local files. Elementor added the feature in version 3.27 (https://developers.elementor.com/elementor-3-27-developers-update/).

For a full walkthrough of each toggle, read What Are Elementor's Performance Settings and How Do You Use Them?. Change one setting at a time, save, and check the page. If two settings change at once, you cannot tell which one helped.

How do you cut the size of an Elementor page?

Remove widgets, sections, and effects the page does not need, because each one adds HTML, CSS, or JavaScript.

Count the widgets on your slowest page. A page with 40 widgets asks the browser to do far more work than a page with 12 widgets, even when the two pages look similar to a visitor.

Use these cuts first:

  • Replace a slider with one static image and a heading when the slider does not earn clicks.
  • Replace nested sections with a single container where the layout allows it.
  • Remove entrance animations from below-the-fold content, since they add JavaScript and delay the visible result.
  • Delete hidden widgets instead of hiding them, because hidden widgets can still load assets.
  • Use one font family with 2 weights instead of 3 families with 5 weights.

Elementor's own 3.31 update shows how much small cuts add up. Its Icon Box CSS fell by over 50%, from over 10 KB to less than 5 KB, after its layout display changed from block to flex (https://developers.elementor.com/elementor-3-31-developers-update/).

The same update cut the CSS added for pages using the Mask feature by half, and moved ribbon styles for Call to Action and Price Table widgets into a separate stylesheet that loads only when the ribbon is used (https://developers.elementor.com/elementor-3-31-developers-update/).

If you are weighing Elementor against a lighter builder, read Block Editor vs Elementor: Speed and Flexibility Compared. The comparison helps when a new page does not need a builder at all.

How do you make Elementor images load faster?

Use the smallest image size that still looks sharp, and never lazy-load the hero image.

Upload images at the size they display, not at full camera size. A 4000-pixel-wide photo shown at 800 pixels wide still downloads at full size unless WordPress serves a smaller copy, so pick the right size in the Image widget settings.

Follow these image rules on every Elementor page:

  • Set the image size in the widget to “Medium Large” or “Large” instead of “Full” when the display size is smaller.
  • Add width and height values, or let WordPress add them, so the browser reserves space and the layout does not jump.
  • Compress images before upload, and use a modern format such as WebP when your host and tools support it.
  • Keep the hero image as a normal image element, not a CSS background, so the browser can find it early.

web.dev breaks LCP into four parts: Time to First Byte at about 40%, resource load delay under 10%, resource load duration at about 40%, and element render delay under 10% (https://web.dev/articles/optimize-lcp). A slow hero image inflates the load duration part, while a late-discovered image inflates the load delay part.

Do not lazy-load the image that PageSpeed Insights names as the LCP element. Lazy loading tells the browser to wait, which is right for below-the-fold images and wrong for the first image a visitor sees.

How do you stop unused scripts and styles from loading?

Remove the add-ons and widgets a page does not use, and keep only one plugin for each job.

Elementor loads scripts for the widgets on a page. Add-on packs add more. If 3 add-on packs are active but a page uses only 1 widget from them, the page still carries the cost of the extra code.

Check the plugin list under “Plugins > Installed Plugins” and deactivate add-ons you no longer use. Then open the page and confirm that nothing on it breaks before you delete anything.

Elementor 3.27 also loads Swiper.js only when a widget needs it, instead of on all pages (https://developers.elementor.com/elementor-3-27-developers-update/). That change helps sliders, but it does not cancel out a page that loads 5 slider plugins at once.

Avoid loading the same feature twice. One caching plugin, one image optimization plugin, and one form plugin are enough for most sites. Two plugins doing the same job can fight over the same files and slow the page.

What server and hosting settings matter for Elementor?

Check PHP, memory, and the server response time first, because no page setting can fix a slow server.

Elementor's system requirements, as of November 2026, are WordPress 6.8 or greater, PHP 7.4 or greater, and MySQL 5.6 or greater or MariaDB 10.5 or greater (https://elementor.com/help/requirements/). Those are minimums, not targets, so ask your host for a current PHP version.

Memory matters just as much. Elementor lists a WordPress memory limit of 256 MB for Elementor and Elementor Pro only, 512 MB recommended, and 768 MB for best performance (https://elementor.com/help/requirements/). If your limit sits at the WordPress default, complex pages can run short.

Check your current values under “Tools > Site Health > Info > Server” in the WordPress admin. That screen lists the PHP version and memory limit your site actually runs with.

If Time to First Byte is high on every page, even simple ones, the cause is usually the server or the database, not one widget. Ask your host about server-level caching, PHP workers, and the database before you rebuild pages. For the full requirements picture, read What Are the WordPress Hosting Requirements?.

How do you use caching with Elementor?

Add page caching, then clear and regenerate Elementor's own files after every change.

Page caching stores a finished HTML copy of a page. The next visitor gets that copy instead of waiting for WordPress and Elementor to rebuild the page from scratch.

Follow these steps in order:

  1. Back up the site, or at least the database, before you change caching settings.
  2. Turn on your host's page cache first if one is offered, since server-level caching is usually the simplest option.
  3. If your host offers no cache, install one caching plugin and use its default page cache settings.
  4. Open “Elementor > Tools” and click “Regenerate Files & Data” so Elementor rebuilds its CSS files from the current settings.
  5. Clear the page cache, then load the page twice: the first load builds the cache, and the second load shows what a visitor gets.
  6. Re-run PageSpeed Insights and compare the new numbers with the ones you saved at the start.

Elementor stores its generated CSS in “/wp-content/uploads/elementor/css/”, and its flush-css command deletes those cached CSS files and recreates them from the settings in the database (https://developers.elementor.com/docs/cli/flush-css). The “Regenerate Files & Data” button in the admin does the same job without the command line.

If a style change does not appear on the front end, regenerate Elementor files and clear the page cache before you edit the design again. Stale CSS is a common cause of phantom speed and style problems. For cache setup at the CDN layer, read How to Set Cloudflare Cache Rules for WordPress.

How do you check that the changes worked?

Re-run PageSpeed Insights on the same page, on the same device type, and compare the numbers you saved.

Run the test 2 or 3 times and look at the middle result, because a single run can catch a slow moment. Compare mobile and desktop separately, since the same page can pass on desktop and fail on mobile.

Check these 3 things after each change:

  • LCP: did the largest content appear sooner, and is it at or under 2.5 seconds?
  • CLS: did the layout stop jumping, with a score at or under 0.1?
  • INP: does the page respond to clicks and taps within 200 milliseconds?

Also open the page in a private browser window and scroll through it. A fast score means little if a section is missing, a font did not load, or a form broke after a setting changed.

Field data takes time to update, because it reflects real visits over a rolling window. Lab results change at once, but the field numbers in PageSpeed Insights and Search Console can take days or weeks to catch up.

What mistakes should you avoid?

Do not stack 3 caching plugins, install a new optimizer for every warning, or change 5 settings at once.

The most common mistakes are easy to avoid once you know them:

  • Installing 2 or 3 caching plugins at the same time, which can serve stale pages or break the layout.
  • Lazy-loading the hero image, which delays the very element LCP measures.
  • Hiding heavy widgets instead of deleting them, so their assets still load.
  • Adding a new add-on pack for one widget, then leaving the pack active on every page.
  • Judging a fix from one PageSpeed Insights run instead of 2 or 3 runs.
  • Skipping the backup before a caching or PHP change, then having no way back.

Elementor's free version already includes over 40 widgets, and its WordPress.org page reports over 10 million active installations (https://wordpress.org/plugins/elementor/).

With that many sites running the same builder, the difference between a fast page and a slow one is usually the choices on the page, not the builder alone.

If you are deciding whether the paid version adds speed value, read Elementor Free vs Pro: What You Get.

Frequently asked questions

Does Elementor make WordPress slow by itself?

Not by itself. Elementor adds HTML, CSS, and JavaScript to each page, and a page with many widgets, large images, and add-ons loads more slowly than a plain page. A lean Elementor page on a good host with caching can load quickly, while a heavy page on a slow server will not.

Should I use a caching plugin with Elementor?

Yes, in most cases. Page caching stores a finished copy of each page so the server does not rebuild it for every visitor. Use your host cache first if one is offered, or one caching plugin. After any change, regenerate Elementor files under Elementor > Tools and clear the page cache.

Why is my Elementor page slow on mobile but fast on desktop?

Mobile devices have slower processors and often slower connections, so the same page costs more to render. Large hero images, many widgets, and extra scripts hurt mobile most. Check the mobile result in PageSpeed Insights separately, shrink the hero image, and remove widgets that mobile visitors do not need.

Do I need Elementor Pro to speed up my site?

No. The main speed features, including Optimized Markup and Element Caching, are in the free version, and caching, image sizing, and hosting fixes do not need Pro. Pro adds widgets and design tools, which can make a page heavier if you add them without a reason.

How long does it take to speed up an Elementor site?

The settings and page cleanup in this guide take about 1 to 2 hours for a small site with a few key pages. Measuring before and after adds another 30 minutes. Larger sites with many templates take longer, so fix the home page and the top landing pages first.

Sources

  1. Elementor Agent Ready Website Builder WordPress.org
  2. System Requirements to Use Elementor Elementor
  3. Elementor 3.31 Developers Update Elementor Developers
  4. Elementor 3.27 Developers Update Elementor Developers
  5. Widget Output Caching Elementor Developers
  6. Defining the Core Web Vitals Metrics Thresholds web.dev
  7. Optimize Largest Contentful Paint web.dev

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