Websites

Elementor vs a Custom WordPress Theme: Comparison and Our Switch

Elementor vs a Custom WordPress Theme: Comparison and Our Switch

Elementor is enough when the site is small, its layout changes often and the team wants to build pages without a developer. A custom WordPress theme wins when speed and stable Core Web Vitals matter, when you want fewer plugins to update and when editors should fill reusable templates with content rather than redesign every page. We’ve made the switch ourselves: in November 2026 we moved orbitbuilder.pl from Elementor and 24 plugins to a theme of our own. Five plugins remain, and post-launch tests show a CLS of 0, an LCP under 0.5 seconds on desktop and Lighthouse scores of 99–100.

How does Elementor differ from a custom theme?

Elementor is a page builder plugin. It gives you a visual editor where pages are assembled from sections, containers and widgets by drag and drop. It stores the layout in its own format in the database (post meta, including _elementor_data) and adds its own styles, scripts and markup to the front end. The theme underneath is often little more than an empty frame.

A custom theme is code written for one specific site: PHP templates, CSS and JavaScript that load only what each page needs. Content is edited in the WordPress block editor (with blocks and patterns built for the brand), in form fields, or in a data structure the editor fills in. Between those two poles sits a third option: a block theme with custom blocks and locked patterns.

Criterion Elementor (with Pro) Block theme with custom blocks Bespoke custom theme
Layout editing Full freedom in the visual editor Freedom within the prepared blocks and patterns Layout designed once; changes go through a developer
Content editing In the same editor as the layout In the WordPress block editor In fields, blocks or data built for the site
Performance Depends on discipline and the number of add-ons Good, since the block editor is part of core Full control over every byte
Plugin count The builder plus, usually, add-on packs Lower Lowest
Content portability Poor: the layout lives in the builder’s format Good: blocks are a WordPress standard Good, if content is kept in standard structures
Upfront cost Lowest Medium Highest
Running cost Highest: updates, conflicts, performance fixes Medium Lowest once the layout is stable

Performance: where does the gap come from?

A page builder has to support any layout anyone might click together. Hence nested containers, styles and scripts loaded just in case, and icon, animation and slider libraries of which a given page uses a fraction. A custom theme loads only what each template needs.

The CMS chapter of HTTP Archive’s Web Almanac 2025 puts it well. Page builders affect DOM complexity, asset loading and script execution, which makes them a major source of performance variation across WordPress sites. The authors note that newer builders load assets conditionally, minify them and rely less on shortcodes, but that these efforts don’t completely close the gap between builder-heavy sites and more tightly controlled builds.

DOM size is easy to check yourself. Lighthouse warns when the body has more than roughly 800 nodes and flags an error above roughly 1,400 (Chrome for Developers). Builder pages with many sections cross those lines quickly, because every widget comes with its own wrappers.

What Elementor has improved

Elementor isn’t standing still. In version 3.32 (September 2025), Element Caching, which stores the rendered HTML of static widgets, became active by default on all sites. The Optimized Markup change, which cuts down widget wrappers, was pulled back from default activation in the same release (Elementor Developers). A fast Elementor site is possible, then, but it takes discipline: one add-on pack or none, restrained animation, self-hosted fonts and manual control over hero images.

Whatever the tool, field data from real visits has the final say. We explain how to read and improve it in our guide to Core Web Vitals.

SEO: does Elementor hurt rankings?

Not by itself. Google doesn’t judge a page by the tool it was built with. A builder does make a few mistakes easier, and we see them in audits all the time:

  • Headings used for styling. An H2 picked because it “looks right”, not because it opens a section. The content structure stops making sense to search engines and screen readers.
  • Separate sections for mobile and desktop. The same content built twice and hidden with CSS depending on the device. It ends up in the HTML twice.
  • The hero image as a CSS background. The browser only discovers it after downloading the stylesheet, which delays LCP, and the image has no alt text.
  • Content in tabs, sliders and pop-ups. Key information tucked away in components that render with JavaScript.
  • Structured data from several sources. The builder, an SEO plugin and the theme each output their own schema.org fragment, and they contradict each other.

With a custom theme you solve these once, at template level: one heading structure, one set of structured data, an LCP image in the HTML with high priority. For more on structured data for search engines and AI models, see our article on schema.org and llms.txt.

Security and maintenance

Most WordPress security problems don’t start in core; they start in plugins. In Patchstack’s State of WordPress Security in 2026, 91% of the 11,334 new vulnerabilities found in 2025 were in plugins, 9% in themes and just 6 in core. On top of that, 46% of vulnerabilities had no fix available when they were publicly disclosed.

Elementor’s ecosystem includes hundreds of add-ons from third-party developers, and the more popular an add-on, the harder attackers look at it. One example: CERT-EU documented a critical vulnerability, CVE-2023-32243 (CVSS 9.8), in the Essential Addons for Elementor plugin. Versions 5.4.0 to 5.7.1 allowed anyone to take over any user’s privileges, administrators included; the fix shipped in 5.7.2 (CERT-EU). That isn’t an argument against Elementor itself so much as against the sprawling set of add-ons that usually surrounds it.

A custom theme shrinks the attack surface but shifts responsibility to whoever built it. Make sure the code lives in a repository, is documented, uses standard WordPress mechanisms and that your contract says clearly who owns it. For the full hardening checklist, read our WordPress security checklist.

Content editing: who will be changing the site?

This question decides more projects than performance does. Elementor gives marketing complete freedom, and freedom has a price: after a year every page looks slightly different, spacing and colours drift, and one careless edit can break the mobile layout.

A custom theme flips that balance. Editors don’t design pages; they fill in prepared fields and blocks, so they can’t break the grid or the typography. The cost is flexibility: a new type of section that wasn’t in the design is a job for a developer. A good middle ground is often the block editor with custom blocks and patterns that can be locked so editors change content but not structure (Block Editor Handbook).

Three questions before you decide

  1. How often does the layout change, and how often the content? If you change the layout once a quarter and the content every week, a builder’s freedom buys you little.
  2. How many templates repeat? Ten services, a hundred posts or a thousand products on the same template make the case for code that’s optimised once for all of them.
  3. Who will own the site in two years? If nobody in the company will keep add-ons updated, a shorter plugin list is worth having for its own sake.

Cost: upfront and ongoing

Item Elementor Custom theme
Design and build Lower, because ready-made widgets and templates do part of the work Higher, because templates and components are built from scratch
Licences An annual Pro licence and usually paid add-ons Usually none, or a few plugins
Updates Frequent, with a risk of conflicts between builder and add-ons Less frequent, fewer moving parts
Performance fixes Recurring: caching, optimisation plugins, fighting the weight Rare, because performance is designed in
Layout changes Cheap, the team does them Need a developer

Actual figures depend on the number of templates, features and languages. We show how to budget for a website, running costs included, in how much does a website cost.

When should you choose Elementor, and when a custom theme?

Situation Sensible choice
A campaign landing page for a few months Elementor or a simple template, as long as it’s light
A small business, a handful of pages, marketing changes the layout, tight budget Elementor with discipline: no add-on packs, self-hosted fonts, controlled images
A site that has to win customers from Google: a blog, many services, several languages A custom theme or a block theme with custom blocks
A WooCommerce store with a large catalogue A lean custom theme: the product template repeats across thousands of URLs
A site with animation, 3D or unusual interactions Custom code; a builder will get in the way
An Elementor site that works and performs fine Keep it, tune performance and trim the add-ons

Our switch: orbitbuilder.pl without Elementor

Until November 2026 our own site ran on Elementor with 24 plugins. As part of a rebrand, we moved it to a theme written from scratch. Five plugins remain. Here is what changed in practice:

  • Two languages without a translation plugin. The theme handles the Polish and English versions, their URLs and hreflang tags. The multilingual plugin is no longer needed.
  • SEO in code, not in a plugin. Meta tags, the sitemap and structured data come from the theme, from a single source, so nothing is duplicated. We dropped the separate SEO plugin.
  • Self-hosted fonts. Two typefaces in trimmed character sets instead of requests to a third-party server.
  • Scripts and styles built with Vite. Each template loads only its own assets, including a lightweight Three.js scene in the background.
  • 301 redirects from the old Polish URLs to the new structure, so we keep our history in Google.

Post-launch tests show a CLS of 0, an LCP under 0.5 seconds on desktop and Lighthouse scores of 99–100, 3D scene included. Those are lab results; field data in the Search Console Core Web Vitals report will follow once Google has collected enough visits. In fairness, we also gave something up: on our site a new section is added by a developer, not by marketing. For a site whose layout changes a few times a year, that’s a good trade for us. The same month we also cleaned the site up after a hack, which I write about in our WordPress security checklist.

How do you move from Elementor to a custom theme without losing SEO?

  1. Take an inventory. Every URL, title, description, heading, redirect and piece of structured data on the current site, plus a Search Console export showing which pages earn clicks.
  2. Measure the baseline. Core Web Vitals, plugin count, load times of the main templates. Without them you can’t prove the result.
  3. Keep URLs or plan redirects. Every URL that changes or disappears gets a 301 to its closest equivalent, following Google’s guidance on site moves with URL changes.
  4. Move the content, not the layout. Content from Elementor sections goes into the new templates. It’s a good moment to fix headings and delete duplicated mobile sections.
  5. Build and check a staging version blocked from indexing, including forms, analytics and cookie consent.
  6. Launch and monitor. Submit the new sitemap and keep watching indexing reports and 404s in Search Console for the following weeks.
  7. Clean up. Remove Elementor, its add-ons and leftovers in the database only once you’re sure nothing depends on them.

We lay out the full migration plan on our page about website migration without losing SEO.

Is your Elementor site slow or hard to maintain? We’ll tell you whether fixes will do or whether a website redesign makes more sense. See how we approach website design and development, or get in touch and send us your URL.

Frequently asked questions

Does Elementor slow down a website?

It can, though it doesn’t have to. Page builders increase DOM complexity and load extra styles and scripts, and according to the Web Almanac 2025 even newer optimisations don’t fully close the gap with tightly controlled builds. A fast Elementor site is possible with few add-ons, self-hosted fonts and controlled images.

Is Elementor bad for SEO?

Google doesn’t judge a page by the tool used to build it. A builder does make mistakes easier: headings used for styling, duplicated mobile and desktop content, hero images as CSS backgrounds and structured data from several sources. With discipline, an Elementor site can rank well.

How much does a custom WordPress theme cost?

More up front than a builder site, because templates and components are built from scratch. In return you pay less for licences, updates and performance fixes. The price depends mainly on the number of page types, features and languages, so we quote it individually.

Can I edit content myself on a custom theme?

Yes. You edit text, images, posts and pages in the WordPress admin, in blocks or fields built for your site. You only need a developer when you want a completely new type of section or a change to a template’s layout.

Will moving off Elementor cost me Google rankings?

Not if you treat it as a migration: inventory your URLs, keep them or 301-redirect them, carry over titles, descriptions and structured data, and watch Search Console after launch. Short fluctuations can happen; lasting drops usually come from missed redirects or deleted content.

When should I stay on Elementor?

When the site is small, you change its layout yourself often, you have no performance or security problems and the budget for a rebuild is limited. In that case it’s better to trim add-ons, sort out caching and images and keep up with updates than to rebuild a working site.

Sources

  1. HTTP Archive – Web Almanac 2025: CMS (page builders)
  2. Elementor Developers – Elementor 3.32 Developers Update (4 September 2025)
  3. Chrome for Developers – Avoid an excessive DOM size
  4. Patchstack – State of WordPress Security in 2026
  5. CERT-EU – Security Advisory 2023-029: Critical vulnerability in Essential Addons for Elementor (CVE-2023-32243)
  6. WordPress Developer Resources – Theme Handbook
  7. WordPress Developer Resources – Block Editor Handbook
  8. Google Search Central – Site moves with URL changes
  9. web.dev – Web Vitals

Need help with this?

We design and code company websites from scratch — no off-the-shelf templates, built for conversion, speed and visibility in Google and AI search.