Elementor or custom code? What the price difference actually buys
The short version. Elementor is not a bad tool and it is often all a small site with simple content needs, even though HTTP Archive data shows only 36% of Elementor sites have good Core Web Vitals on mobile, against 53% of all sites. The decision changes when the site has to win business and be maintained and extended for years. If you are comparing offers for web development, compare the cost over three years and not only the launch price.
Why two suppliers quote such different prices
A page builder is a visual editor. The site is assembled from ready-made blocks, so it goes up quickly. That is why it tends to be cheaper, and there is nothing suspicious about that.
With custom code, a developer writes what that particular site needs. We use WordPress with Bedrock and the Sage theme. It takes longer, so it costs more. Both sites can look equally good. The difference shows in speed, maintenance and the first larger change.
| Page builder | Custom code | |
|---|---|---|
| Launch | faster and cheaper | slower and more expensive |
| Content edits | you can usually click through them yourself | as agreed, depending on what is made editable |
| Code on the page | generic, more nested elements | only what the page uses |
| Speed | depends on discipline, add-ons and hosting | depends on the developer and hosting |
| Dependency | on the builder, its add-ons and licences | on the developer and the documentation |
A good developer can build a fast site on Elementor too. A weak one can ruin custom code as well. The tool guarantees nothing by itself, so ask about the result.
Speed: what the public data says
HTTP Archive publicly compares technologies using data from real Chrome users. This is the share of sites with a good result on mobile for September 2026:
| Technology | Core Web Vitals overall | Loading (LCP) | Responsiveness (INP) | Server (TTFB) |
|---|---|---|---|---|
| All sites | 53% | 66% | 79% | 46% |
| WordPress overall | 48% | 55% | 90% | 23% |
| Divi | 41% | 48% | 94% | 18% |
| Elementor | 36% | 41% | 88% | 15% |
What follows from it:
- The weak spot is loading, not responsiveness. Elementor sites respond to clicks better than the web as a whole. The data does not support the claim that a builder mainly ruins interaction.
- The server may be a large part of the problem. 15% of Elementor sites have a fast server response, against 46% of all sites. One possible reason is that smaller projects on cheap hosting often pick a builder.
- The table does not prove the cause. It shows how sites using a technology perform, not why. Better hosting can help an Elementor site without a rebuild.
This data has no separate “custom code” category, so we will not give you a number for how much faster it is. Measure the specific site instead, the method is below.
Security: every add-on is one more supplier
WordPress itself is not the main problem. For 2025, Patchstack recorded 11,334 new vulnerabilities, 91% in plugins, 9% in themes and only 6 in WordPress core. For 46% of them, the developer’s fix was not ready in time for public disclosure.
For builders it matters that the threat is often not the builder itself, but add-on packs from other authors. The top ten most exploited vulnerabilities in the same report include an older flaw in the Startklar Elementor Addons plugin (up to version 1.7.13), which allowed uploading a file to the site without logging in. The flaw was not in Elementor but in an add-on for it. This is how risk builds up on websites.
That is why regular website care matters, along with how many unnecessary dependencies the site has at all. If you fall under NIS2, this is also a question of supplier responsibility.
What about AI search?
One myth needs correcting here. Elementor sends finished HTML from the server, so AI crawlers can read the text. The claim that they cannot see it because of the builder does not hold up. When a site is missing from AI answers, the cause is usually elsewhere: content without concrete facts, weak brand signals, or important information locked in images and PDFs. We also wrote about whether to block AI crawlers.
Compare offers over three years
A simple formula: development + care + hosting + add-on licences, all over 36 months. Also add what a change costs if you cannot make it yourself.
An example with our prices: a Business website from €1,990 and yearly care at €440 come to at least €3,310 over three years, plus hosting. Care includes one hour of work per month and extra work costs €40/h. A smaller site of up to 5 subpages starts at €990. Break down the other offer the same way. Sometimes it stays cheaper, and then there is no reason to pay more.
What to ask a supplier before you sign
- What will the site be built on, and why that? A good supplier explains it without jargon.
- What will I be able to edit myself, and what does the rest cost? Have it listed.
- Who pays for builder and add-on licences, and whose account are they on? When a licence ends, updates can end too.
- Who handles updates and backups, and when did you last test a restore?
- How will we measure speed at handover? Agree on the tool, the pages and mobile.
- Will I get the code and all access if I leave one day? Get the answer in the contract.
How to find out what your current site runs on
- Open the page source (in Chrome Ctrl+U, on a Mac Cmd+Option+U) and search for
elementor. For Divi search foret_pb. If the word keeps repeating, the site is built in a builder. - Measure the site in PageSpeed Insights on the Mobile tab. Look mainly at data from real users, if Google has it. LCP, the loading of the main content, should be within 2.5 s and INP, the response to a click, within 200 ms. Lab scores fluctuate, so do not draw conclusions from one measurement.
- Check the plugin list in the admin. Find out who updates them and whether you still need them all.
A builder in the source code is not a problem in itself. If the site is fast, updated and brings enquiries, do not change it just because someone is selling you a new technology.
When to choose what
A builder is enough when you have a small site, want to click through most changes yourself, the budget is tight and the site is not your main source of business.
Custom code pays off when the site wins business, you target Google in several languages, you need integrations with other systems, or you want speed and dependencies under control.
A rebuild pays off only when you can name what your current site is costing you.
Frequently asked questions
Is WordPress slow? Not by itself. Speed depends on what is built on it and on the hosting.
Will I be able to edit a custom-coded site myself? As agreed. The blog and the parts you change often can be prepared for you to edit. Other changes are made by a developer, so agree on this before the project starts.
Can an Elementor site be sped up without a rebuild? Often yes: remove unused add-ons, simplify pages, improve hosting and caching. Only when that is not enough does a new site make sense.
Status as of 3 November 2026. Prices are “from” prices. Measurement tools change between versions, so always compare with the same tool.
Sources: Patchstack: State of WordPress Security in 2026, HTTP Archive: Technology Report, web.dev: Largest Contentful Paint, web.dev: Interaction to Next Paint.
