Page builders: what Elementor, Divi and WPBakery cost a page
A builder ships its framework on every page and wraps every element in extra markup. Measure its share of the code and the DOM, then turn on its performance settings.
Step by step, with screenshots: Divi performance: the settings that actually cut page weight →
Check your own site
Runs this check and the other 192, free, in about 45 seconds.
Or run only this check with the free Unused CSS/JS checker.
What it is
Page builder weight is how much code a visual builder such as Elementor, Divi or WPBakery adds to a page: its framework CSS and JavaScript, icon fonts, animations and the extra nested containers around every element. The builder loads much of this on every page, whatever the page actually uses.
When the builder becomes most of the code and most of the HTML, the browser has more to download, parse and lay out before the visitor sees content, and every other speed fix has less effect. Builders have added performance options in recent versions, but they are not always switched on for older sites.
OK looks like this: the builder's performance settings are on, unused widgets and add-on packs are off, and the builder is a minority of the page's CSS and JavaScript. getReport measures the builder's share in percent and KB and names the setting to try first.
What a passing site looks like
- Page builder weight: passeswarning · −1.5 ptseffort M
Page builder weight
Why it matters. A page builder ships its whole framework on every page, whatever the page uses, and wraps every element in extra containers. When it becomes most of the code and most of the markup the visitor downloads and the browser lays out, every other speed fix has less to work with.
- Switch on the builder's own performance settings first: see the report for the exact setting
- Remove widgets, animations and add-on packs the page does not use; each one adds its own CSS and JavaScript.
- For the pages that matter most (home, key landing pages) consider building them with core blocks and the theme alone, and keep the builder for the rest.
Questions people ask
Does Elementor slow down your site?
It can. Elementor adds its own CSS and JavaScript, icon fonts and nested wrapper elements, so an Elementor page is usually heavier than the same design built with core blocks. With its performance features on, unused widgets disabled, good hosting and caching, Elementor sites can still pass Core Web Vitals.
Why is Elementor so slow?
Mostly because of what it loads and how much HTML it produces: global widget styles and scripts, Font Awesome and eicons, animations, third-party add-on packs and deeply nested sections. Turn on the settings under Elementor's Performance and Features tabs, remove add-ons you do not use, and avoid heavy effects above the fold.
Is Elementor bad for SEO?
No, not directly. Search engines read Elementor pages like any other. The risks are speed, since heavier pages can fail Core Web Vitals, and structure, since it is easy to choose headings by size instead of level. Set heading tags deliberately and keep the page light, and Elementor pages can rank well.
How do you make a page builder faster?
Switch on the builder's own performance options first, such as optimised DOM output and loading assets only for widgets on the page. Then remove unused widgets, add-on packs, animations and icon libraries, cache the pages, and consider building the most important pages with the block editor.