WordPress page builders (Elementor, Divi, Bricks)

Overview

WordPress page builders are visual drag-and-drop editors that sit on top of (or in place of) WordPress's native block editor (Gutenberg). The dominant commercial builders in 2026 are Elementor, Divi (Elegant Themes), WPBakery, Beaver Builder, and Bricks. As of 2025-2026 they collectively render the majority of all small-business WordPress sites, but every published metric — market share, page weight, security, lock-in, and pricing — has moved against them since 2023.

This page consolidates the knowledge base's atomic entries on page builders into a single reference. It documents:

• Market share figures (2025 Web Almanac; W3Techs April 2026; WordPress.org install counts).
• Performance cost (Anubiz's 500KB / 2,000-DOM-element measurement; corewebvitals.io's 3.8–5.2s pre-optimization LCP; WPPoland's 40% speed gain on Elementor → Gutenberg migrations; Elementor's own 40%-less-HTML admission for Flexbox Containers).
• Breakage history (Elementor 3.24.1 August 2024; Elementor 3.26 Schemes API removal; FAQ JSON-LD caching bug; open accessibility issue #11779; deactivate-with-content feature request #5667 open since 2018; absence of default schema markup).
• Pricing-power asymmetry (Elementor Pro's November 2023 Essential-tier strip; Bricks's January 2024 retirement of its $199 lifetime deal; Divi 5's February 26, 2026 one-way migration).
• Bricks Builder's strengths (cleanest output among visual builders in 2026) and its February 2024 CVE-2024-25600 unauthenticated RCE (CVSS 10.0), exploited in the wild within ~24 hours of patch.
• Migration economics (Elementor-to-Gutenberg rebuild treated as a full content rebuild rather than a code conversion; GeneratePress's official position that Elementor code cannot be converted to block-editor code).
• A standing rule and four-stage transition roadmap for moving an SMB agency's default new-build stack off page builders and onto Gutenberg + a block theme.

The voice is encyclopedic and neutral. Confidence labels from the underlying entries are preserved verbatim.

Related research briefs: Agency methodology for small-business website projects and Core Web Vitals contain the longer argumentative form; this page is the reference layer.

Market share (2025–2026)

2025 Web Almanac, CMS chapter, Fig. 12.6

The 2025 Web Almanac (CMS chapter, Figure 12.6) gives the following 2025 share of WordPress sites on mobile, with 2024 comparison:

Builder	2025 share of WP sites (mobile)	2024 share	Direction
Elementor	43%	56%	losing share fast
WordPress Block Editor (Gutenberg)	18%	~12%	growing fast
WPBakery	13%	21%	declining
Divi	10%	14%	declining
Beaver Builder	~2%	~2%	flat
Bricks	<2% (not in top 5)	–	growing, no public number

Approximately 60% of WordPress sites use some form of page builder according to the 2025 Almanac. Headline movement 2024 → 2025: Elementor share fell from 56% to 43% (a 13-percentage-point drop), while Gutenberg grew from roughly 12% to 18%. WPBakery and Divi both declined.

Live-site counts:

• Elementor: 10+ million active installs (wordpress.org/plugins/elementor/).
• Divi: ~2.16 M live sites (BuiltWith via Colorlib).
• WPBakery: ~2.32 M live sites (WebTechSurvey).
• Bricks: not publicly disclosed (commercial-only, no .org listing). Pricing: $99/site or $249 lifetime historically; see Bricks pricing section below.

Confidence: Verified for the Almanac shares and Elementor official install count; high-confidence for Divi/WPBakery via BuiltWith/WebTechSurvey.

W3Techs (April 2026)

W3Techs's Elementor detail page, fetched April 19, 2026, reports:

"Elementor is used by 18.6% of all the websites whose content management system we know. This is 13.2% of all websites."

Source: https://w3techs.com/technologies/details/cm-elementor. Confidence: Verified.

The 18.6%-of-known-CMS figure refines an earlier W3Techs snapshot of 13.1% recorded in mid-2025. The newer number reflects continued growth in Elementor's absolute footprint even as Elementor's share of the page-builder market declines (Colorlib reports Elementor at 40-50% of page-builder market, down from 56% peak in the 2024 Almanac). The two trends are compatible: total WordPress installs continue to grow; Elementor's slice within WordPress is shrinking; its absolute install count is still rising. Elementor remains the de-facto default for small-business WordPress in 2026.

Comparison datum: Beaver Builder Lite shows 100,000+ active installations on WordPress.org — roughly two orders of magnitude smaller than Elementor.

Defining "live": three separable meanings

Headline install counts conflate distinct definitions of a "live" site. "Live" has at least three separable meanings, and they diverge:

1. Subscription active — the customer is still paying the platform.
2. Domain resolving — the URL still loads something.
3. Content actually updated within period — the site is being maintained, not just preserved.

A site can satisfy (1) and (2) while failing (3). A site can satisfy (2) while failing (1) (e.g. domain points at vendor parking). Independent data exists for (1) and (2) at the platform level; (3) is survey-based and survivorship-biased. Outcomes — leads / sales — are a separate fourth category with essentially no platform-segmented data.

Source: Synthesis of platform-magnitude entries in the consolidated KB.

Confidence: Framework / synthesis.

The earliest primary-source acknowledgement of the gap between registration and publication comes from Wix's Form F-1 (SEC, March 20, 2014), which states verbatim:

"The length of time that users take following registration to design and publish a website varies significantly from hours to years, and many users never publish a website. We have no means of assessing the level of engagement of a particular user following registration…"

Source: SEC EDGAR — Wix.com Ltd. Form F-1, March 20, 2014.

Confidence: Verified (primary SEC document).

The disclosure is a primary-source admission by the leading hosted builder that (a) launch failure exists and (b) the platform does not measure it. Any "X million installs" or "X million sites" figure cited in this section should be read against the same caveat: install or subscription counts do not equal published, maintained, or commercially active sites.

Performance cost

Pre-optimization median mobile LCP: 3.8–5.2 seconds

corewebvitals.io's 2026 WordPress guide reports that Elementor sites typically show a median mobile LCP of 3.8–5.2 seconds before optimization — well above Google's 2.5-second "good" threshold. Post-optimization typically lands at 2.0–2.8 seconds, but the same source notes that this requires "ongoing maintenance as plugin and builder updates frequently reintroduce bloat."

Source: https://www.corewebvitals.io/core-web-vitals/wordpress-guide (2026). Confidence: Industry-consensus.

The implication is architectural rather than tactical. The Elementor performance penalty is not a one-time fix; it is a maintenance posture. Every plugin update, every theme update, and every new widget can regress LCP back over the 2.5s threshold. For sites that require stable Core Web Vitals — typically those competing on transactional intent in markets where SERP performance still matters — the recurring optimization spend is structurally embedded in the architecture choice.

Anubiz Host: 500KB+ CSS/JS per page, 2,000+ DOM elements

Anubiz Host's Elementor → Gutenberg migration analysis documents two specific measurements:

• "Elementor adds 500KB+ of CSS/JS to every page"
• "A simple page can have 2,000+ DOM elements"

A companion finding from Seismic Pixels notes that page builders nest "five, six, or seven layers deep" of <div> tags around a single paragraph.

Sources: https://anubizhost.com/seo/migrate-elementor-to-gutenberg ; https://seismicpixels.com/gutenberg-blocks-vs-page-builders-seo/ . Confidence: Single-source (vendor blog) for the specific numbers; industry-consensus for the pattern.

These numbers exceed any reasonable SMB performance budget (typical targets: total uncompressed page weight ≤1.0 MB, compressed JS initial bundle ≤150 KB, compressed CSS ≤50 KB) before the site has loaded any of its own content. Per-page weight from the builder alone is regularly several times what a disciplined performance budget targets. The Anubiz number compounds with third-party tag overhead: Chrome Aurora and Web Almanac measurements show GTM containers loading 18+ tags can multiply Total Blocking Time by an order of magnitude. Page builders are the foundation cost; tag managers are the additive cost.

Elementor's own 40%-less-HTML admission (Flexbox Containers)

Elementor's own engineering blog (2023–2024) states:

"Containers produce 40% less HTML output than sections and columns for the same layout."

Confidence: Verified (vendor admission).

The significance is structural. Pre-Container Elementor — sections/columns, the default for most builds before 2022 — emits 40%+ more HTML than the new Flexbox-Containers system. Sites built before 2022 are still on the old section/column system unless they have been migrated. The vendor has acknowledged the cost; the customer has paid it.

Even with Flexbox Containers, page builders still emit deeply nested <div> structures (five-to-seven layers around a single paragraph is typical per Seismic Pixels and Anubiz). Container adoption reduces the cost but does not eliminate the structural pattern.

WPPoland: 40% mobile speed gain on Elementor → Gutenberg rebuilds

WPPoland, an agency citing dozens of client migrations, reports that Elementor → Gutenberg rebuilds yield "a 40% increase in mobile site speed" on average.

Source: https://wppoland.com . Confidence: Single-source (vendor portfolio aggregation).

The vendor publishes this number to sell rebuild engagements, so it should be treated as directional. The direction-of-effect is consistent with Anubiz's structural-overhead measurements and Elementor's own 40%-less-HTML admission. The "40%" figure recurs across independent sources — Elementor's own engineering data, Anubiz's third-party measurement, and WPPoland's portfolio aggregation. The convergence suggests the number is approximately real.

Breakage history

The maintenance cost of page builders is dominated by post-update incidents. Each release of Elementor or Divi is a potential outage for sites that have not staged the update on a non-production environment. The following are the canonical 2024–2026 incidents.

Elementor 3.24.1 (August 2024): widespread site breakage

Elementor 3.24.1 (August 2024) shipped with breaking changes. The WordPress.org support thread titled "Elementor update broke my site and its entire design" documents widespread reports of full design loss.

Source: https://wordpress.org/support/topic/elementor-update-broke-my-site-and-its-entire-design/ . Confidence: Verified.

At agencies that maintain WordPress portfolios, page-builder update incidents are the largest single source of "site broke after update" tickets in the maintenance retainer time budget. Each incident typically consumes 4–20 hours of remediation across a client portfolio (see Cost catalogue, item 1, below).

Elementor 3.26 (late 2024): Schemes API removal + Element Caching default

Elementor 3.26 (late 2024) removed the legacy Schemes API and enabled Element Caching by default. Elementor's own release warning reads:

"This change is considered very risky, especially for websites that use Elementor add-ons not hosted in the official plugin repository."

Source: https://sitecare.com/elementor-326-errors/ . Confidence: Verified (Elementor team's own statement).

This is a "very risky" admission from the vendor itself. When a platform vendor characterizes its own release as "very risky" for sites running third-party add-ons, every Elementor maintenance contract is exposed to that risk. Schema markup bugs cascaded from this release (see FAQ schema bug, next subsection).

Elementor FAQ Accordion + Element Caching: FAQPage JSON-LD "Missing field text"

Pronto Marketing documented a downstream consequence of the 3.26 Element Caching default: Elementor's FAQ Accordion widget breaks the FAQPage JSON-LD output. Google Search Console reports the structured-data error "Missing field 'text'."

Source: https://www.prontomarketing.com/blog/fix-elementor-faq-schema-bug/ . Confidence: Verified.

Two compounding costs follow:

1. Lost AI Overview citations. FAQPage schema is one of the primary signals AI extraction systems (Google AI Overviews, Perplexity, ChatGPT extension fetches) use to pull verbatim answers. Broken FAQ schema means lost mentions.
2. Google Search Console errors. The property is flagged as having broken structured data, which surfaces as a recurring nag in the SEO maintenance loop.

This bug is a direct downstream consequence of the 3.26 Schemes API removal documented above.

Elementor accessibility: open Issue #11779

Elementor GitHub Issue #11779 is open. The issue text from the Elementor team itself reads:

"Unfortunately, Elementor is not fully compliant out of the box and breaks many of the rules for accessibility."

Source: https://github.com/elementor/elementor/issues/11779 . Confidence: Verified (the issue is open on Elementor's own repo; the language is acknowledgement, not allegation).

The structural problem is twofold. First, the default Elementor output is not WCAG-compliant. Second, Elementor's Pro accessibility tools (the "Ally" widget) sit behind the paid Pro plan — accessibility is positioned as a paid upsell rather than a default. The EU European Accessibility Act has been enforceable since June 28, 2025; ADA Title II compliance deadlines for state and local government digital content extend into 2027–2028. Default-accessible output not being the default — with remediation gated behind upsell — sits within the broader regulatory pattern that culminated in the FTC's January 2025 $1 million settlement with overlay vendor accessiBe over deceptive accessibility-overlay claims. The lesson: accessibility overlay widgets are not accessibility solutions; accessibility is an architectural property, not a layered patch.

Elementor #5667: no "deactivate with content" since 2018

Elementor has no built-in mechanism to deactivate and retain content as standard HTML/WordPress markup. This is tracked as a still-open feature request on GitHub: elementor/elementor issue #5667.

Sources: GitHub elementor/elementor issue #5667; Nelio Software analysis; WordPress Help Blog migration guides. Confidence: Industry-consensus.

The implication is that Elementor lock-in is structural rather than malicious. The builder's data model is fundamentally different from WordPress's native post_content. Practical exit requires one of:

1. A content rebuild on the order of a small new-site engagement, treated as a full rebuild rather than a code conversion (see GeneratePress migration position in the Migration by use case section).
2. Commercial migration tools (Nelio, etc.).
3. Staying on Elementor.

Parallel lock-in patterns: Divi 4 stored content as proprietary [et_pb_*] shortcodes, leaving pages full of unrendered shortcode tags when the theme is disabled (Elegant Themes blog; Divi documentation 2025-2026, Verified — Divi 5 adopts a block-based format but the carve-out remains for the millions of existing Divi 4 installs). Advanced Custom Fields (ACF) field data is lost in the standard WordPress XML export, so backups that look complete frequently are not.

Elementor: no schema markup by default

Schema Pilot:

"[Elementor] does not generate schema markup. None of the layouts, widgets, or templates you build in Elementor add structured data."

Source: https://www.schemapilot.app/blog/elementor-schema-markup/ . Confidence: Verified.

Schema is a hygiene layer that AI extraction systems rely on for verbatim answer pulls; it is not, by itself, a ranking growth lever. Elementor produces none of it. Sites built on Elementor without an additional schema plugin (RankMath, Yoast, AIOSEO) are missing the entire hygiene foundation.

The WooCommerce-specific bug: Elementor GitHub Issue #9529 (open since 2019) documents that WooCommerce product pages built with Elementor are marked up as WebPage items instead of Product — breaking shopping-result rich snippets entirely.

Elementor Pro pricing strip (November 2023)

WP Tavern, November 2023:

"Elementor Pro is removing things like ACF/Pods integration from their lowest tier 'Essential' plan."

Source: https://wptavern.com/elementor-pro-pricing-update-slashes-features-in-the-essential-plan-for-new-customers . Confidence: Verified.

This is the classic SaaS pricing-power pattern. Once a platform has market share, features migrate up the pricing tiers and the entry tier strips down. Existing customers on grandfathered plans are not affected immediately, but new customers face the new economics. Combined with Elementor's recurring-only model (no lifetime license available; auto-renewal required) and the shift toward credit-based Elementor One, the trajectory is consistent: price escalation is the platform's only direction.

The comparison case is Bricks's January 2024 retirement of its $199 unlimited-sites lifetime license — see Bricks pricing section below. The framing connector is Agency methodology for small-business website projects.

Divi 4 → Divi 5: a one-way migration

Divi 5 entered beta in November 2022 and removed the beta label on February 26, 2026 — a 3+ year development cycle that disrupted customer projects. Elegant Themes documents that Divi 4 stores "all layout data as shortcodes… [Divi 5] replaces shortcode-based layout storage with a new, more stable storage format." Migration between the two versions is a one-way data conversion.

Elegant Themes Help Center:

"Switching from Divi 4 to Divi 5 is a one-way update via the Migrator… the longer you run Divi 5 and edit content, the harder a clean rollback becomes."

Sources: https://elegantthemes.com/blog/divi-resources/how-to-migrate-your-website-to-divi-5 ; https://help.elegantthemes.com/en/articles/12767407-how-to-safely-migrate-from-divi-4-to-divi-5 . Confidence: Verified.

This is the page-builder lock-in pattern made explicit by the vendor itself. Rollback degrades over time: "the longer you run Divi 5 and edit content, the harder a clean rollback becomes." That asymmetry is the architectural reason every client engagement should produce a verifiable database export on day one — before any builder is allowed to write content into a proprietary format.

The Divi 4 shortcode architecture is documented in the breakage history section above: every Divi 4 layout writes [et_pb_section]…[et_pb_text]… shortcodes into post_content. Disabling the Divi theme leaves shortcode soup in every post, which is why most Divi exits are full rebuilds.

Bricks Builder

Bricks is the only page builder worth considering when a client absolutely cannot work in Gutenberg.

Cleanest output among visual builders (2026)

Among WordPress visual page builders, Bricks produces the cleanest HTML/CSS/JS output — comparable to Gutenberg on simple pages, with 95+ PageSpeed Insights typical (PageBuildLab, PureThemes 2026 testing). Bricks is a theme replacement (it occupies the theme slot rather than installing as a plugin on top of an existing theme). It stores content as JSON in postmeta._bricks_page_content_2.

The lock-in is real but cleaner than the alternatives: Bricks stores content as JSON in postmeta — still locked to the builder, but cleaner than Divi's shortcode-in-post_content or Elementor's JSON blob in postmeta. Migration to markdown / Portable Text / Astro Content Collections is still essentially impossible — plan to rebuild pages on migration.

Confidence: Directional. Bricks does not publish install counts; performance claims are from independent agency testing.

Recommendation hierarchy: Gutenberg > Bricks > Beaver Builder > Elementor > Divi > WPBakery.

CVE-2024-25600: unauthenticated RCE, exploited in 24 hours

Bricks Builder ≤ 1.9.6 contained an unauthenticated remote code execution vulnerability (CVE-2024-25600), CVSS 10.0. Patchstack disclosure:

"[Allows] any unauthenticated user to execute arbitrary PHP code on the WordPress site."

Patch 1.9.6.1 shipped February 13, 2024. Active exploitation in the wild was detected from February 14, 2024 — approximately one day after patch availability.

Source: https://patchstack.com/articles/critical-rce-patched-in-bricks-builder-theme/ . Confidence: Verified.

This is the "page builders are the highest-value attack surface" thesis in a single CVE. Bricks runs on tens of thousands of sites; an unauthenticated RCE means anyone on the internet could execute PHP as the web user. Attackers had patch-diff exploits live within 24 hours of disclosure. Page builders are, by code volume, one of the largest plugins on a typical site — their attack surface scales accordingly.

Ecosystem context (Patchstack 2026, Feb 25, 2026): 11,334 new vulnerabilities in the WP ecosystem in 2025 (+42% YoY); 91% in plugins; weighted median time to first exploit: 5 hours; 46% had no patch at disclosure.

Bricks retired $199 unlimited-sites lifetime license, January 2024

Bricks Builder retired its $199 unlimited-sites lifetime license in January 2024. Current pricing (2026): $79–$249/year subscription, or $599 one-time (Ultimate, unlimited sites).

Source: https://bricksbuilder.io/pricing/ . Confidence: Verified.

This is textbook inflection-point pricing. Bricks built its reputation on the $199 lifetime deal; once enough sites had committed to it, the deal went away. Customers who bought before January 2024 keep their lifetime entitlement; new customers pay 3–4× as much for the same feature set. Adjacent precedents: Shopify's forced sunset of checkout.liquid customizations on Plus stores (cascading 2024–2026 deadlines) and Elementor Pro's November 2023 Essential-tier strip both follow the same template — once a platform has switching cost on its side, the pricing power activates.

Cost catalogue: 10 categories, ranked by long-term cost

The full ranking of page-builder costs to a small-business site, highest first:

1. Compounding maintenance debt. Every plugin update is a potential break. Documented incidents: Elementor 3.24.1 August 2024 breakage, Elementor 3.26 Schemes API removal, Bricks CVE-2024-25600, Divi 4 → 5 one-way migration February 2026. 4–20 hours of remediation per incident across a client portfolio.
2. Lock-in / migration cost. A full content rebuild rather than a code conversion when leaving a page builder for Gutenberg — see Migration by use case below. The cost of admission that no vendor discloses at sale.
3. Performance penalty. WordPress's overall mobile Core Web Vitals pass rate sits at roughly 43%, well below platforms like Duda (~84%) per CrUX/HTTP Archive 2025 reporting; page-builder sites trend toward the lower end of the WordPress distribution. See the Anubiz 500KB / 2,000-DOM-element measurement above.
4. AI citation invisibility. OtterlyAI's 2026 1M-citation study and Cloudflare's January–July 2025 crawler logs both confirm GPTBot, ClaudeBot, and PerplexityBot fetch raw HTML without executing JavaScript at scale. Page-builder JS-dependent rendering reduces extractable content. This cost compounds through 2026–2027 as AI search share grows.
5. Accessibility legal exposure. EU EAA enforceable since June 28, 2025; ADA Title II deadlines for state and local government digital content extend into 2027–2028. Page-builder defaults fail WCAG 2.1 AA without paid remediation (Elementor Issue #11779); the FTC's January 2025 $1M settlement with overlay vendor accessiBe sets the precedent that bolt-on overlays are not a defensible remediation strategy.
6. Schema markup gaps. No native structured data (Elementor schema markup section above); FAQ accordion bugs (Pronto Marketing); WooCommerce product schema broken since 2019 (Issue #9529).
7. Pricing-power asymmetry. Once built on a builder, the vendor restructures pricing (Elementor Pro November 2023), retires deals (Bricks January 2024), or forces migrations (Divi 4 → 5 February 2026). The site owner has no exit that isn't a rebuild.
8. Security attack surface. Page builders are among the largest plugins on a site. CVE-2024-25600 is one CVE; Patchstack 2026 reports 91% of WP vulns in plugins, median time to first exploit 5 hours.
9. Developer/agency dependency. The "client can edit it" myth means the agency holds the keys regardless; retainer revenue is structurally subsidized by the architecture choice.
10. Architectural inflexibility. Custom components, headless preview, multi-channel content reuse — all more expensive when content is trapped in proprietary builder blobs.

Decomposing "dead builder site" attribution

A common failure mode in evaluating builder platforms is attributing site abandonment to the builder when the underlying business has shut down. US Bureau of Labor Statistics Business Employment Dynamics data establishes the baseline:

~20–22% of US establishments fail in year 1; five-year survival is ~49.6% for the canonical March 1994 cohort and ranges 49.8–57.3% across cohorts per BLS Table 7 ("Survival of private sector establishments by opening year"); ~65% have failed by year 10.

Source: US BLS Business Employment Dynamics, Table 7.

Confidence: Verified (government data).

The implication for builder-cost analysis: roughly half of any cohort of small businesses is gone within five years regardless of platform choice. When evaluating "dead site" prevalence among Elementor, Wix, or any other platform, the BLS curve is the first baseline — site abandonment in those years is dominated by business closure, not platform failure. The page-builder costs above are real and additive; they are not the primary driver of abandonment in the first five years.

Site-staleness data and its limits

A frequently cited figure is that ~25% of small-business websites are updated less than once a year, also rendered as "43% update content less than monthly" in a 2025 SMB digital barometer.

Source: Survey-based; multiple aggregators; 2025 SMB digital barometer.

Confidence: Single-source to Industry-consensus.

Caveat — survivorship: These surveys measure still-live sites only. Abandoned sites are excluded by construction, so the true population staleness is almost certainly higher than the headline figure suggests. The number is a useful directional input for "live but frozen" inventory, not a population-level statistic.

Migration by use case

GeneratePress's official forum position, the definitive statement of the structural lock-in problem:

"You cannot convert Elementor's code to the code required by the Block Editor. So if you disable Elementor you will be left with just the unstyled content."

Source: GeneratePress official forum. Confidence: Verified.

The lock-in is structural, not contractual. Disabling Elementor leaves unstyled content in the post (the text survives — Elementor does not use shortcodes); the design is unrecoverable. Disabling WPBakery leaves shortcode soup. Beaver Builder is the cleanest exit of the four major builders.

Scalebloom and Crocoblock both describe practical Elementor-to-Gutenberg work as a full content rebuild on a similar order to a fresh small-site engagement rather than a code conversion. Crocoblock notes that Elementor is at least cleaner to migrate than WPBakery, Bold Builder, and UX Builder, which use shortcodes pervasively.

For per-use-case stack recommendations (existing-portfolio inheritance vs. greenfield brochure vs. content-led SEO build vs. WooCommerce), see Agency methodology for small-business website projects.

When a hosted builder (Wix, Squarespace) is the correct choice

Evidence and practitioner consensus converge that DIY hosted builders are the correct, sufficient choice for:

• Simple brochure / "digital business card" sites (about, services, contact).
• Early-stage businesses testing an idea where speed and low cost beat customization.
• Budget- and time-constrained owners without technical staff, who value bundled hosting / security / SSL and a single support contact.
• Low-stakes sites where the business does not depend on granular SEO, complex integrations, or high traffic.

Source: Practitioner consensus; capture-layer synthesis.

Confidence: Industry-consensus.

This is a legitimate positive finding, not a research failure. The case against WordPress page builders does not extend to "all builders are wrong for all SMBs"; for the use cases above, a hosted DIY builder is often the correct architecture and a custom WordPress build is over-spec.

Owner time investment: data is conflicted

Published estimates for owner build/maintenance hours range widely: a weekend (1–3 days) for a simple site; 10–40 hours including learning and troubleshooting (one DIY-vs-pro guide); 30–50+ hours including SEO and accessibility; one agency claims "190–400 hours" for full DIY competence.

Source: Mix of builder marketing, agency content, practitioner guides.

Confidence: Directional-Speculative.

Caveat — every source is conflicted: Builders minimize the number (they sell speed); agencies maximize it (they sell the alternative to DIY). No reliable independent study isolates owner build/maintenance hours. Treat the entire range as conflicted; any client-facing claim must state "no reliable independent data" and cite the range with conflicts named.

Page-builder to block-theme migration: the observed transition pattern

A neutral, third-person summary of how WordPress agencies are observed moving their default stacks off page builders and onto block themes between 2023 and 2026. The pattern is documented across multiple agency case studies (WPPoland, Multidots, Seahawk Media, Anubiz Host) and is consistent with the four published evidence bases summarised earlier in this page: performance penalty, breakage history, lock-in cost, and accessibility exposure.

The observed transition typically proceeds in stages rather than as a single cutover. First, agencies stop adding new builds to the page-builder stack and pick a block-theme alternative (Kadence, GeneratePress, Blocksy, or the default Twenty Twenty-Five) for any subsequent new-build work. Second, they document a standardised starter kit — block theme plus ACF Blocks for bespoke modules — and run new builds on it long enough to measure honest build-hour ratios against prior page-builder builds; published agency reports note that the first few Gutenberg builds frequently take longer than equivalent Elementor builds before block-editor fluency catches up. Third, existing page-builder clients are offered a migration audit at their next redesign cycle rather than reflexively rebuilt. Fourth, content-heavy and SEO-sensitive clients become the candidate pool for headless Astro + WordPress pilots, which preserve the WordPress authoring layer while removing the page-builder render path.

The benchmarks that change the transition pattern are external. If WordPress core stewardship destabilises further — for example a recurrence of the 2024–2026 Automattic vs WP Engine dispute that materially affects Gutenberg's roadmap — Bricks Builder becomes a managed-risk option whose output is cleaner than Elementor's. If a Gutenberg regression ships in a 6.x release that materially degrades block-editor UX, the case for Beaver Builder as a stability play strengthens. If AI search referral traffic does not become a meaningful channel by mid-2027, the AI-extractability argument behind the transition weakens proportionally.

The supporting evidence base, summarised across the page above and the Sources and confidence table below, falls into seven categories: performance (the corewebvitals.io, Anubiz Host, and WPPoland measurements); lock-in (GeneratePress's published position that Elementor markup cannot be converted to block-editor code); pricing power (Elementor Pro's November 2023 Essential-tier strip and Bricks's January 2024 retirement of its unlimited-sites lifetime licence); security (Bricks CVE-2024-25600, exploited approximately twenty-four hours after the patch shipped); accessibility (Elementor GitHub Issue #11779, open on Elementor's own repo); schema (the Schema Pilot finding that Elementor generates no structured data by default, plus the Pronto Marketing FAQ-accordion JSON-LD bug); and AI extractability (OtterlyAI's 2026 million-citation report plus Cloudflare's January–July 2025 crawler logs, both showing that AI crawlers do not execute JavaScript at scale).

Sources and confidence

Claim / datum	Source	Confidence
Elementor 43% of WP sites (2025); Gutenberg 18%; WPBakery 13%; Divi 10%	2025 Web Almanac, CMS chapter, Fig. 12.6	Verified
Elementor 10M+ active installs; Beaver Builder Lite 100,000+	WordPress.org plugin directory	Verified
Divi ~2.16 M live sites; WPBakery ~2.32 M	BuiltWith via Colorlib; WebTechSurvey	High
Elementor 18.6% of known-CMS sites, 13.2% of all websites	W3Techs, fetched April 19, 2026	Verified
"Many users never publish a website"	Wix.com Ltd. Form F-1, SEC EDGAR, March 20, 2014	Verified
Median mobile LCP 3.8–5.2s pre-optimization; 2.0–2.8s post	corewebvitals.io WordPress guide (2026)	Industry-consensus
Elementor adds 500KB+ CSS/JS; 2,000+ DOM elements/page	Anubiz Host migration analysis	Single-source (vendor blog) for the specific numbers; industry-consensus for the pattern
Five-to-seven nested <div> layers around one paragraph	Seismic Pixels	Industry-consensus
Flexbox Containers ship 40% less HTML than sections/columns	Elementor engineering blog (2023–2024)	Verified (vendor admission)
40% mobile speed gain on Elementor → Gutenberg rebuilds	WPPoland portfolio aggregation	Single-source (vendor)
Elementor 3.24.1 broke sites and designs (Aug 2024)	wordpress.org/support thread	Verified
Elementor 3.26 removed Schemes API + Element Caching default ("very risky")	sitecare.com/elementor-326-errors/	Verified (vendor statement)
FAQ Accordion JSON-LD "Missing field text" bug	Pronto Marketing	Verified
"Elementor is not fully compliant out of the box"	GitHub elementor/elementor issue #11779 (open)	Verified
No "deactivate with content" since 2018	GitHub elementor/elementor issue #5667 (open); Nelio Software; WordPress Help Blog	Industry-consensus
Elementor generates no schema markup; WooCommerce → WebPage not Product (Issue #9529)	Schema Pilot; GitHub issue #9529	Verified
Elementor Pro Essential tier stripped (ACF/Pods removed) Nov 2023	WP Tavern	Verified
Divi 5 released Feb 26, 2026; one-way migration; rollback degrades	Elegant Themes blog + Help Center	Verified
Bricks cleanest output among visual builders; 95+ PSI typical	PageBuildLab, PureThemes 2026 testing	Directional
CVE-2024-25600 unauth RCE CVSS 10; patch Feb 13 2024; exploited Feb 14 2024	Patchstack	Verified
2025: 11,334 new WP vulns (+42% YoY); 91% in plugins; median TTFE 5 hrs; 46% unpatched at disclosure	Patchstack 2026 (Feb 25, 2026)	Verified
Bricks $199 unlimited-sites lifetime retired Jan 2024; current $79–$249/yr or $599 one-time	bricksbuilder.io/pricing/	Verified
"You cannot convert Elementor's code to Block Editor code"	GeneratePress official forum	Verified
Elementor → Gutenberg treated as full content rebuild, not code conversion	Scalebloom; Crocoblock; GeneratePress	Industry-consensus
~20–22% Y1 establishment failure; 49.6% five-year survival; 65% failed by Y10	US BLS Business Employment Dynamics, Table 7	Verified
~25% of SMB sites updated less than yearly; 43% less than monthly	Survey aggregators; 2025 SMB digital barometer	Single-source to Industry-consensus
AI crawlers (GPTBot, ClaudeBot, PerplexityBot) do not execute JS at scale	OtterlyAI 1M-citation report 2026; Cloudflare crawler logs Jan–Jul 2025	Industry-consensus

Linked KB entries (kept standalone, not absorbed): Agency methodology for small-business website projects, Core Web Vitals, Agency methodology for small-business website projects.