Elementor slows a website down when its performance settings are left off, when a site uses several add-on packs and dozens of widgets it doesn't need, when layouts are built from deeply nested sections, and when it runs on hosting that's too weak for a page builder. To speed it up, turn on Elementor's built-in performance options, remove unused add-ons and widgets, simplify layouts (Flexbox containers instead of nested sections), use global fonts and colours with fewer font files, optimise images, add proper caching, and make sure your hosting and PHP version meet Elementor's requirements. A slow editor, as opposed to a slow live site, is mostly about hosting resources, PHP memory and add-ons.

I'm Rustam from Frame the Pixel, a web design and maintenance studio in Kuala Lumpur. I build and maintain a lot of Elementor sites, often with Crocoblock, and I like Elementor. But I also see plenty of slow ones, and the reasons are nearly always the same.

First: is it Elementor, or something else?

Before blaming the builder, measure. Run the page through PageSpeed Insights on mobile and check the Core Web Vitals against Google's thresholds. Then check:

Server response time. If the server is slow to respond on a simple page, the problem is hosting or caching, not Elementor.
Image sizes. Large images slow any site, built with anything.
Third-party scripts. Chat, tracking and embedded video add weight regardless of builder.

If the site is slow for reasons beyond Elementor, my general guide, why is my WordPress site so slow, covers twelve causes. The rest of this post is about the Elementor side.

1. Turn on Elementor's performance features

Elementor has added a number of performance features over the years, and on older sites many of them are still switched off because they arrived after the site was built. Depending on your version, look under Elementor, Settings, in the Performance and Features tabs. Options to look for include:

Optimised DOM output, which removes extra wrapper elements from the page code.
Improved asset loading, so scripts and styles for a widget only load on pages that use it.
Improved or inline CSS loading.
Inline font icons, which avoids loading whole icon font libraries.
Loading Google Fonts locally rather than from Google's servers.
Element caching, which saves the output of widgets so they don't have to be rebuilt each time.
Lazy loading of background images.

Turn them on one at a time on a staging copy, and check the site after each. Some older custom code or add-ons don't like a change in the page structure. Elementor's help centre explains each option for your version.

2. Move from sections and columns to containers

Older Elementor layouts use sections, inside them columns, inside them inner sections and more columns. Every level adds HTML. Flexbox containers do the same job with far fewer elements.

For new pages, build with containers.
For key existing pages, such as the home page and landing pages, Elementor offers a converter, but treat the result as a draft. I usually rebuild the most important pages cleanly rather than convert them.
Avoid nesting containers more than you need. Two or three levels usually do.

3. Cut the add-ons and widgets you don't use

Hands lifting excess wooden beads off a tray into a ceramic bowl, like removing unused Elementor add-ons and widgets

Elementor add-on packs are tempting, because each one adds dozens of widgets. But many load their scripts and styles on every page, even when you use one widget from the whole pack.

List every Elementor add-on plugin. For each, write down which widgets you actually use.
If you use two widgets from a pack of eighty, see whether Elementor or another add-on you already have can replace them.
Most add-on packs let you disable unused widgets in their settings. Do that, even if you keep the pack.
In Elementor's own settings, you can also disable unused core widgets on newer versions.

In my experience, trimming add-on packs is often one of the biggest single wins on an older Elementor site, though every site differs and it's worth measuring before and after.

4. Use global fonts and colours, and fewer of them

Every font family and weight is another file to download. Elementor makes it easy to pick a different font in every widget, and sites end up loading six families without anyone deciding to.

Set global fonts and colours in Site Settings, and use them everywhere.
Stick to one or two families and only the weights you use.
Load fonts locally (see step 1).

5. Be careful with motion, sliders and effects

Entrance animations, parallax, sticky effects, motion effects and sliders all add JavaScript and can hurt Interaction to Next Paint and layout stability. Sliders at the top of the page are often the slowest element on the page and delay Largest Contentful Paint.

Replace a home page slider with a single strong image or a static layout.
Keep animations to a few meaningful places, not every heading.
Avoid video backgrounds on mobile.

6. Optimise images inside Elementor

Upload images at the size they'll appear, not straight from a camera.
Use WebP or AVIF.
Set image sizes in widgets rather than always choosing "Full".
Don't lazy load the main image at the top of the page.

7. Get caching right for Elementor

Elementor pages cache well. Use your host's cache or one caching plugin, and clear the cache after editing. If you use a plugin to minify and combine files, test carefully, as combining Elementor's files can break layouts. When the site looks broken after an update, regenerating Elementor's CSS files (Elementor, Tools, Regenerate files and data) often fixes it.

8. Check hosting and PHP

Page builders do more work on the server than hand-coded themes, especially in the editor. Elementor publishes its requirements, including PHP version and memory. Running a current, supported PHP version with enough memory makes both the site and the editor faster.

Why the Elementor editor is slow

A slow editor is a different problem from a slow live site, because the editor can't use page caching. Common causes:

Not enough PHP memory or a slow server. The editor loads a lot at once.
Too many add-ons, each adding its widgets and controls to the editor panel.
Very long pages with many widgets. Split them or use templates.
A browser extension interfering, especially ad blockers. Try a private window.
Other plugins loading heavy scripts in the admin. Query Monitor on staging shows which ones.

A quick Elementor speed checklist

A plain white paper aeroplane resting on a clean oak desk, representing a fast lightweight Elementor website

Work through these in order, testing on staging after each change:

Measure with PageSpeed Insights and note the scores.
Check hosting response time and caching.
Update Elementor, Elementor Pro and add-ons.
Turn on performance features one by one.
Remove or trim add-on packs and disable unused widgets.
Set global fonts, cut font families and load them locally.
Replace sliders and trim animations.
Optimise images.
Convert or rebuild key pages with containers.
Measure again and compare.

What not to do

Don't stack optimisation plugins. Two caching or minifying tools fighting each other often make an Elementor site slower and break layouts.
Don't switch every performance feature on at once on the live site. If something breaks, you won't know which setting caused it.
Don't judge by the desktop score alone. Most visitors are on phones, and mobile is where heavy Elementor pages hurt.

Keeping an Elementor site fast

Speed slips as add-ons update, pages are added and new scripts appear. Regular maintenance catches it. My post on Elementor website maintenance covers the routine for Elementor and Crocoblock sites, and if an update has just broken your layout, see what to do when a WordPress update broke your site.

Want a faster Elementor site?

I speed up Elementor sites as part of my website maintenance service, and when a site needs more than tuning, I rebuild key pages cleanly through my website design and development work. I work 9am to 5pm Malaysia time (GMT+8) with clients in Malaysia, the UK, Europe and beyond. Get in touch or email contact@framethepixel.com with your web address.

FAQ

Does Elementor slow down WordPress?

It can, but it doesn't have to. With performance features on, few add-ons, container layouts and good hosting, Elementor sites can pass Core Web Vitals. Most slow Elementor sites are slow because of how they were built.

Why is the Elementor editor so slow?

Usually low PHP memory or slow hosting, too many add-ons, very long pages, or a browser extension. The editor can't use caching, so it shows how hard your server is working.

Should I switch from Elementor to make my site faster?

Not usually as a first step. Tuning settings, cutting add-ons and rebuilding key pages with containers often fixes it. A full rebuild is worth considering only if the site has bigger design or structural problems.

Are Elementor containers faster than sections?

Generally yes, because they produce less HTML for the same layout. The difference is biggest on complex pages with many nested sections.

Will caching fix a slow Elementor site?

Caching helps visitors a lot, but it won't fix heavy pages, large images or a slow editor. Use it alongside the other steps.