Why your Elementor site is slow — and 9 fixes that work

"Elementor is slow" is one of the most repeated claims in WordPress circles. It's partly true: a page builder adds code that a hand-coded theme doesn't. But most slow Elementor sites are slow for reasons that have little to do with Elementor itself. These are the fixes that make the biggest difference, roughly in order of impact.

1. Start with decent hosting

No amount of optimization fixes a server that takes two seconds to respond. Look for hosting with a modern PHP version, server-level caching and enough resources for your traffic. If your Time to First Byte is consistently slow, this is where to start.

2. Turn on page caching

Without caching, WordPress builds every page from scratch for every visitor. A caching plugin, or your host's built-in cache, serves a ready-made copy instead. For WooCommerce and membership sites, make sure the cart, checkout and account pages are excluded.

3. Use a lightweight theme

When Elementor builds your header, footer and pages, a heavy multipurpose theme is just loading code you never use. Hello Elementor is designed to be the thinnest possible base for Elementor sites.

4. Cut down add-on plugins

Elementor add-on packs are tempting: hundreds of extra widgets for free. But many load their CSS and JavaScript on every page, whether you use their widgets there or not. Three add-on packs for five widgets is a common cause of bloat. Keep the ones you really use and replace the rest with built-in widgets.

5. Use Elementor's performance settings

Elementor has performance options in its settings, covering things like loading only the CSS and scripts a page needs and producing leaner HTML. Recent versions turn most of them on by default, but older sites often still have them off. It's worth checking, then testing the site afterwards.

6. Build with containers

Older Elementor layouts used sections, columns and inner sections, which produce a lot of nested HTML. Flexbox and grid containers achieve the same layouts with far fewer elements. Fewer elements means less work for the browser and a faster, more responsive page.

7. Be strict with fonts

Every font family and every weight is another file to download. Two families and three or four weights cover almost any design. Elementor can load Google Fonts from your own server instead of Google's, which saves a connection and is better for privacy. Make sure fonts use font-display: swap, so text appears straight away.

8. Optimise images

Images are usually the heaviest part of a page. Upload them at sensible sizes, serve modern formats like WebP or AVIF, and lazy-load everything below the fold. I've covered this in detail in image optimization for WordPress.

9. Go easy on the first screen

Sliders, background videos and entrance animations on the hero section all delay the moment the main content appears. That moment is measured as Largest Contentful Paint, one of the Core Web Vitals. A strong static hero image with a clear headline usually converts better anyway.

Measure before and after

Run PageSpeed Insights on your key pages before you change anything, and again afterwards. Test real pages, not just the homepage, and look at the mobile results, which are almost always worse.

If your Elementor site feels sluggish, send me the link and I'll tell you where the time is going.