Elementor Is the Most Popular WordPress Page Builder, and It Passes Core Web Vitals Least Often

Elementor is the most popular way to build a WordPress site. It runs on nearly a million of the origins in this study, more than any other page builder. It is also the builder least likely to load quickly for the people who actually visit those sites. Just 30.0% of Elementor sites pass Google's Core Web Vitals on mobile, the lowest pass rate of any major builder, and below the 41.5% posted by the block editor WordPress ships for free.

That gap is not a technicality. Site speed is the first thing a visitor experiences, before a single word of your copy or a single product image. A page that loads slowly loses people before they see it, drags down conversions, and weakens search rankings, because Google treats Core Web Vitals as a ranking signal. For a small business or a publisher, the builder you assemble your pages in sets a ceiling on all of that.

Page builders have long carried a reputation for weighing sites down, and to see whether it is earned we matched the builder detected on more than two million WordPress sites to how those sites perform for real Chrome users in Google's own field data. The reputation holds, with an important twist about which part of performance suffers.

The numbers here come from two sources joined together. HTTP Archive's technology detection tells us which page builder is running on each WordPress origin, and Google's Chrome User Experience Report tells us how fast that origin actually is for the real people who load it. This is field data from real visits, not a lab score from a single test run. In total the study covers roughly 2.1 million WordPress origins across nine builders, each with a large enough audience to register in Google's data.

A site passes Core Web Vitals only when it is good on all three metrics at once: Largest Contentful Paint under 2.5 seconds (loading), Interaction to Next Paint under 200 milliseconds (responsiveness), and Cumulative Layout Shift under 0.1 (visual stability). We measure at the 75th percentile on mobile, which is the standard Google uses and the harder, more honest test, because it reflects the slower phones and networks a real audience brings rather than a developer's fast laptop.

Rather than write theme code, millions of site owners drag and drop layouts with Elementor, Divi, WPBakery or the newer native block editor. Those tools are convenient, and the field data shows the convenience has a cost. Elementor, the most widely deployed builder in the dataset, passes on 30.0% of its mobile sites. WPBakery sits at 32.7%, Divi at 34.5%. All three trail WordPress's native block editor, Gutenberg, which passes on 41.5% of mobile sites.

Put plainly, the three most popular third-party page builders each make a WordPress site less likely to pass than building with the tools WordPress ships in the box. The convenience of a visual drag-and-drop canvas is real, but so is the weight it adds, and that weight lands squarely on the experience your visitors have.

The twist is where the damage lands. It is not responsiveness. Every builder in the data is good on Interaction to Next Paint for between 92% and 97% of mobile sites. Page builders, whatever else they do, do not flood the main thread with the kind of JavaScript that ruins INP. What they add instead is markup, styles, and images that inflate loading.

A drag-and-drop builder generates the HTML and CSS for whatever layout you assemble, and generic builders tend to output more of both than hand-built or block-native pages: nested wrapper elements, per-section styling, extra fonts and icon libraries, and large hero images placed without much loading discipline. All of that lands on Largest Contentful Paint, which measures how quickly the biggest element on the screen renders. Elementor sites are good on LCP just 44.8% of the time, and that loading weak point drags the overall pass rate down. It is the mirror image of our framework studies, where frameworks fail on INP and page builders fail on LCP.

Elementor deserves its own line because of its scale. At 982,553 mobile origins it is the most-deployed builder here, so its weak pass rate touches an enormous number of real sites. And the diagnosis is precise. Its INP is fine at 92.6% good, and its layout stability is actually strong at 92.3% good CLS. The entire problem is loading: 44.8% good LCP means most Elementor sites take too long to paint their main content on a phone.

That is encouraging, because it points to a fixable class of problem rather than something baked into the builder. Image optimization, reining in the number of widgets and fonts, and good page caching all move LCP directly. An Elementor site owner who is failing is almost never failing on the hard, structural metric. They are failing on the one that responds most readily to cleanup.

Two of the top three, Duda and Webflow, are not WordPress tools at all. They are hosted visual builders with tighter performance defaults, and they pass at nearly double Elementor's rate. Inside WordPress, the tools closest to native rendering, the Block Editor, the Site Editor, and the relatively lightweight Beaver Builder, beat the heavy drag-and-drop trio. The pattern is consistent: the closer a builder stays to the markup WordPress produces on its own, the more often its sites pass. If you have not launched yet and speed matters, it is worth checking how fast the average WordPress site is before you commit.

Duda and Webflow are non-WordPress hosted builders, kept in the ranking for contrast.

The mobile number is the one your visitors feel, so do not read your desktop score and relax. The gap is real on desktop too, with Elementor at 40.3%, Divi at 31.7% and WPBakery at 38.8%, all still trailing Gutenberg's 50.2%. It is simply softer, because faster desktop connections and processors mask heavy pages that a mid-range phone cannot. Divi's 61.7% good CLS on desktop is the one notable weak spot in the table, a reminder that layout stability can slip even where loading looks healthy.

On desktop the gap persists but compresses; Divi's 61.7% good CLS is the notable weak spot.

The builder you choose is a Core Web Vitals decision as much as a convenience one, and for the 982,553 Elementor sites in this study it is costing a pass. If you are already on Elementor, Divi or WPBakery and failing, target loading, not responsiveness: Elementor's INP is good on 92.6% of sites and its CLS on 92.3%, while only 44.8% have good LCP. Optimize the hero image and other large media, cut unused widgets, fonts and icon packs, add page caching, and defer offscreen content. LCP is where these builders lose, and LCP is where the fix is. Our WordPress page builder speed guide lays out how to make a builder fast, step by step.

If you have not committed yet and speed is a priority, staying close to native gives you a better starting point: the Block Editor passes on 41.5% of mobile sites and the Site Editor on 43.8%, against Elementor's 30.0%. The gap holds on desktop too, where Elementor's 40.3% still trails Gutenberg's 50.2%, so a fast connection will not rescue a heavy build. The encouraging part is that nothing here is structural. The most popular builder on WordPress is the slowest today, but the 44.8% good-LCP problem behind that number is the kind a focused afternoon of image and caching cleanup can move.