- Measure first: test your key templates in PageSpeed Insights and note LCP, CLS and INP.
- Images, fonts, too many add-ons and heavy above-the-fold sections cause most slowdowns.
- Caching helps, but it can’t fix a page that is heavy by design.
- If pages are still slow after these fixes, the builder output itself may be the limit.
Elementor makes building pages easy. Over time, though, many Elementor sites get slow: more widgets, more add-ons, bigger images, another slider. Before deciding to rebuild, it's worth fixing the usual suspects. Often that's enough. If it isn't, you'll at least know exactly why.
Measure before you change anything
Run your home page and one or two key templates (a service page, a blog post) through PageSpeed Insights. Note the mobile score and the three Core Web Vitals: LCP (how fast the main content appears), CLS (how much the layout jumps) and INP (how quickly the page reacts to clicks). Keep these numbers so you can see what each fix changes.
9 fixes to try first
1. Compress and resize images
Upload images at the size they're shown, in a modern format like WebP, and lazy-load anything below the fold. Don't lazy-load the main hero image: it delays LCP.
2. Cut the number of fonts
Each font family and weight is another file. Stick to two families and only the weights you use, and host them locally if you can.
3. Remove add-on packs you don't need
Elementor add-on packs often load their scripts and styles on every page, even where no widget is used. Audit them and keep only what you need.
4. Simplify the top of the page
Sliders, video backgrounds and entrance animations in the hero hurt LCP the most. A static image and a headline usually convert just as well and load much faster.
5. Use Elementor's own performance settings
Recent versions include performance options for loading assets more efficiently. Turn them on and test, one at a time.
6. Reduce nesting
Sections inside columns inside sections create a lot of extra HTML. Rebuilding heavy sections with fewer levels makes pages lighter.
7. Set up proper caching
Page caching and a CDN reduce server response time. They help a lot, but they can't make a heavy page light.
8. Delay third-party scripts
Chat widgets, heatmaps and tracking tags can be delayed until the user interacts. This often improves INP noticeably.
9. Check your hosting
If server response time is slow even on a cached page, hosting may be the limit. Most sites have plenty to fix before that, though.
When the builder is the bottleneck
If you've done the above and your key pages are still slow on mobile, look at the page size and the number of DOM elements. When most of the weight comes from the builder's own CSS, JavaScript and wrapper elements, there's only so much you can do in place. That's when rebuilding the slow templates in a lighter builder makes sense. I compare the options in Bricks vs Elementor.
You don't have to choose blindly. On a clinic site I worked on, mobile PageSpeed went from 58 to 94 and desktop from 77 to 97 without changing the design. Sometimes the fix is in place, sometimes it's a rebuild. The speed optimization service starts by telling you which one you need.
Jesús Sisco
WordPress and technical SEO specialist. I move sites from Elementor and Divi to Bricks, build new ones in Bricks, and make sure the rankings come along. Based in Madeira.
Elementor & WordPress speed optimization →