Page builder · WordPress

Why your Elementor site is slow (and how to fix it)

Elementor makes building pages easy, but every section, column and widget adds markup, CSS and JavaScript. Maki scans your Elementor pages with Google PageSpeed Insights and shows which of those costs are actually hurting your Core Web Vitals — then tells you which Elementor setting or plugin option fixes each one.

What usually slows down Elementor sites

01

Deeply nested sections bloat the DOM

Old Section → Column → Widget layouts generate thousands of DOM nodes. Switching to Flexbox Containers and enabling Elementor's Optimized DOM Output usually cuts the count dramatically.

02

Global CSS and icon libraries load everywhere

Font Awesome, eicons and per-widget stylesheets load on pages that never use them. Improved Asset Loading and Inline Font Icons experiments help, and a script manager can unload the rest.

03

Google Fonts block rendering

Elementor loads Google Fonts from an external domain by default. Hosting them locally with font-display: swap removes a render-blocking request.

04

Hero images are lazy-loaded

Background and image widgets at the top of the page are often lazy-loaded, which delays Largest Contentful Paint by seconds.

Elementor speed FAQ

Is Elementor bad for Core Web Vitals?

Not inherently. Elementor sites can pass Core Web Vitals, but the defaults load more CSS, JavaScript and DOM than a lean theme. Most slow Elementor sites are fixed by a handful of settings plus a caching/optimization plugin.

Should I switch to Flexbox Containers?

For new pages, yes. Containers produce far fewer DOM nodes than the legacy section/column structure, which helps both LCP and INP.

Also see: WooCommerce · WP Rocket · Perfmatters · LiteSpeed Cache · Divi

Scan your Elementor site free.

Free scan with real Google data. Exact fixes for your plugins.