Is Elementor slowing your site down? How to check and fix it
Compare an Elementor page with a plain one, see what Elementor loads, then change the settings that help. A 30-minute check, and when to rebuild instead.
By Sohail Hussain19 November 20265 min read
You can find out in about 30 minutes. Measure one of your Elementor pages, build the same content on a plain block-editor page, and compare the two on mobile. If the Elementor page is much heavier and slower, Elementor or its add-ons are a cause, and its own performance settings plus some design discipline will fix part of it. If both pages are slow, the problem is your hosting, caching or images, and removing Elementor would not help.
Elementor alone is rarely the whole story. Slow Elementor sites usually combine it with one or two add-on packs, a heavy theme, fonts loaded from Google, a slider and no page cache. The steps below separate those causes.
If you are still deciding whether to use Elementor at all, read Elementor vs Gutenberg vs a custom theme first. If you want someone else to run this check and fix what it finds, it is routine work in our website design and development projects.
How can you tell if Elementor is the cause?
Step 1: measure a real page. Pick a page built in Elementor that matters, such as the homepage or a main service page. Run it through PageSpeed Insights on mobile three times and note the median: LCP, Total Blocking Time, total page weight and number of requests. Our Core Web Vitals calculator shows which numbers pass Google's thresholds.
Step 2: build a control page. Create a new page, edit it in the block editor rather than Elementor, and add roughly the same content: the same images, headings and text, without the effects. Publish it, leave it out of menus, and measure it the same way. Delete it when you are done.
Step 3: compare. The gap between the two pages is what Elementor and its add-ons cost on that page, on your hosting. A difference of a few hundred kilobytes and a few tenths of a second in LCP is normal, and often acceptable. A difference of a megabyte or more, or whole seconds of LCP, means something on the Elementor side needs fixing.
If the control page is slow too, stop here and work through how to speed up a WordPress site, starting with hosting and caching.
What is Elementor adding to each page?
Step 4: list what loads. Open the Elementor page in Chrome, open DevTools, go to the Network tab and reload. Type elementor in the filter box. You will see Elementor's CSS and JavaScript, Elementor Pro's if you use it, and usually icon fonts. Then clear the filter and sort by size. Look for:
- Add-on packs, under
/wp-content/plugins/, loading files on pages that use none of their widgets. - Requests to
fonts.googleapis.comandfonts.gstatic.com, especially for several families or many weights. - Animation libraries and slider scripts on pages with no visible animation or slider.
Step 5: count the elements. Page builders wrap each piece of content in layers of containers. Lighthouse reports DOM size in its diagnostics, or paste this into the DevTools console on each page:
document.querySelectorAll("*").length
Compare the two pages. Pages built with Elementor's older section-and-column structure usually show the biggest gap, because each section adds several wrapper layers. A large DOM slows rendering and makes every tap feel slower on low-end phones.
Which Elementor settings help?
Step 6: change settings one at a time, and measure after each. Elementor has added several performance options over recent versions. Their names, their place in the settings and their defaults have changed between releases, so check what your version offers:
- Flexbox containers. Containers replaced sections and columns and produce fewer wrapper elements. New sites use them by default. Older pages can be converted section by section; convert your most visited templates first and check them on mobile afterwards.
- Loading Google Fonts locally. Serves the fonts from your own server instead of Google's, which removes connections to two extra domains. Cutting the number of families and weights helps more.
- Inline SVG icons. Draws icons as inline SVG instead of loading whole icon font files. Worth it when a page uses a handful of icons.
- Element caching. Stores the rendered output of widgets so it is not rebuilt on every uncached request. It does not apply to elements with dynamic content. Elementor's own documentation explains the limits.
- Lazy-loading background images. Helps long pages with many background images below the fold. Make sure the hero is not one of them.
Outside the settings, the biggest wins are usually these: remove add-on packs you use one widget from, replace a slider with a single image, and make the hero a real image element at a sensible size instead of a 3 MB background. WordPress can prioritise a real image for loading; it cannot do that for a CSS background.
What else on an Elementor site is usually slow?
The same things as on any WordPress site, which is why step 3 matters. No page cache, or two caching plugins fighting each other. Shared hosting with a slow first byte. Images uploaded straight from a camera. Third-party scripts: chat widgets, heatmaps, several analytics tags. Elementor gets blamed for these because it is the most visible plugin on the site.
One trap is specific to Elementor: the theme underneath. Elementor is designed to run on a light theme such as its own Hello theme. Running it inside a heavy multipurpose theme loads two design systems on every page, and the theme's styles and scripts are wasted on pages Elementor draws completely.
When should you stop tuning and rebuild?
Step 7: decide with numbers. After the settings changes, measure the Elementor page and the control page again. If the gap is now small, you are done. Keep Elementor, and keep the list of add-ons short.
If the Elementor page is still far behind, and the page matters because it gets search or ad traffic or it is where people enquire, rebuild that template in blocks. You do not have to remove Elementor from the whole site at once. Moving the ten most visited templates and leaving low-traffic pages alone is a common, sensible middle path.
A rebuild is not worth it if the field data in PageSpeed Insights already passes Core Web Vitals and enquiries are steady. The gap is real, but it is not costing you anything. For where Elementor fits in a WordPress setup overall, see WordPress for business websites.
Was this guide useful?