Key takeaways
- Elementor is the right tool when you want to edit your own site, launch in weeks and keep the budget in the low thousands.
- Custom code is the right tool when performance is the product, the design cannot be expressed in a builder, or the site is really an application.
- Most problems blamed on Elementor are problems with how it was used. Most problems blamed on custom code are problems with who you depend on afterwards.
What Elementor actually is
Elementor is a visual builder for WordPress. You design pages by placing sections and widgets, and it writes the HTML and CSS for you. I have built sites with it for over ten years, and I still choose it for most business websites, so this is not a neutral article. It is an honest one.
The case for it is practical. A site can be designed and built in the same tool, so changes are fast. The client can edit text, swap an image or add a page without calling anyone. The ecosystem is large: forms, galleries, sliders, booking tools, all exist and all connect. And the cost is lower, because a lot of what a developer would write by hand already exists.
The case against it is also practical. Builders generate more markup than a developer would write, which can make pages heavier. A site depends on the builder and its updates for as long as it lives. And in the wrong hands, Elementor makes it easy to build a slow, inconsistent site, because it never says no.
What custom code actually is
"Custom code" usually means a developer writes the theme by hand: HTML, CSS and a little JavaScript, on top of WordPress or another system, or as a static site with no system at all. Everything is exactly as intended, nothing is loaded that is not needed, and the result can be very fast.
The cost is that every change goes through a developer. The client can edit content in the areas the developer prepared, and nothing else. Adding a new kind of section means a new piece of code. That is fine when the site is finished and stable. It is expensive when the business keeps changing, which most do.
Where each one wins
| Elementor | Custom code | |
|---|---|---|
| Build time | weeks | weeks to months |
| Cost | lower | higher |
| Client edits | pages, sections, layout | content in prepared areas |
| Page weight | heavier, can be tuned | as light as the developer makes it |
| Dependency | on the builder's updates | on the developer's availability |
| Best for | business sites, landing pages, small shops | apps, large publishers, unusual designs |
The part nobody says out loud
The tool is not the main variable. The person is.
A good Elementor build uses a handful of global styles, a consistent set of sections, optimised images and as few plugins as possible. It passes Google's Core Web Vitals and it stays fast as the content grows. A bad one uses a different font size on every page, five sliders and forty plugins, and no tool could have saved it.
The same goes the other way. A good custom build is documented, uses a system the next developer knows, and leaves the client able to edit what they need. A bad one is a brilliant site that only one person on earth can change.
So the question to ask a provider is not "Elementor or code?". It is "show me three sites you built two years ago, and tell me who edits them now".
When I recommend each
I build with Elementor when the site is a business website or a small shop, the client wants to edit it, and the budget is the one most Swiss SMEs have. That covers most of my work.
I recommend custom code, or build it myself, when the site is really an application (a configurator, a client portal, a booking system with rules), when the design relies on effects a builder cannot express, or when the site will have very high traffic and every kilobyte is money.
And I say no to both when a Shopify or Webflow setup would fit the business better. The tool follows the job.
FAQ
Is Elementor bad for SEO?
No. Google ranks what is on the page and how fast it loads. A well-built Elementor site passes Core Web Vitals; a badly built one does not, and the same is true of custom code. Structure, content and speed decide, not the builder.
Will my Elementor site be slow?
Not if it is built with care: sized images in modern formats, few plugins, a caching layer, and the builder's own performance settings switched on. Ask any provider for the Core Web Vitals of three sites they built last year. That is the proof that matters.
What happens if Elementor stops existing?
The pages remain, as WordPress content, and would need rebuilding in another tool. The same applies to any system, including custom code when its developer stops answering. The practical protection is the same in both cases: own your hosting, keep backups, keep your content separate from the layout.
Can I move from Elementor to custom code later?
Yes. The content (texts, images, posts) moves with WordPress. The layout is rebuilt. It is a redesign project, not a migration.
Twenty minutes on the phone, a written quote within two working days.