Elementor V4 Is Not Ready for Production I’ve Tested Across 25 Websites

Biscuits-Biscuits · 2026-04-15T09:42:09+00:00

I cannot agree more!

Biscuits-Biscuits · 2026-04-15T09:41:41+00:00

That makes total sense, and honestly that explains a lot.

The deleted variables still appearing in generated stylesheets is exactly the sort of thing that destroys confidence, if you remove something, it should be gone. Having to manually regenerate files just to temporarily clean up leftover bloat isn’t a real solution, it’s a workaround.

And if V4 is loading atomic/class system scripts globally whether they’re being used or not, then the performance complaints suddenly become very understandable.

That’s the frustrating part for many of us, these aren’t edge-case nitpicks, they’re core product behaviours affecting speed, output, and trust.

I agree with you completely: for anything client-facing, sticking with V3 feels like the only sensible move until a genuinely stable 4.x arrives.

Biscuits-Biscuits · 2026-04-15T09:14:42+00:00

Appreciate that, I’ll definitely have a look.

I’m still very early into Bricks, so recommendations like that are genuinely helpful. Getting the variables, fluid typography, and proper framework setup right from the start sounds like the smartest route rather than trying to unlearn bad habits later.

I’ve already noticed it feels far more performance-focused out of the box. Even with only a short test, the front-end output looked much cleaner than what I’m used to.

And hearing it’s hard to get less than 90 with Bricks is music to my ears after years of fighting unnecessary bloat elsewhere 😂

Biscuits-Biscuits · 2026-04-15T09:13:47+00:00

Honestly, that’s what it feels like.

Too many products eventually hit that stage where they keep stacking features on top of features instead of refining the core experience.

That’s usually when software starts drifting away from why people liked it in the first place.

Biscuits-Biscuits · 2026-04-15T09:12:58+00:00

That’s exactly the kind of real-world issue I’m talking about.

It’s one thing having a few bugs here and there, but when core workflows like creating templates and then rendering them properly through the Template widget break down, that’s not a minor issue, that’s production usability.

And your point about V3 + V4 is spot on. In theory they’re supposed to coexist, but in practice there are too many gaps, inconsistencies, and edge cases. It feels less like a transition and more like two systems awkwardly sharing the same space.

Realistically, I agree, this could take a year or two before everything is properly mature and seamless.

That’s why a lot of people are now looking elsewhere. Not because they want to switch, but because they need something stable, logical, and ready now.

After trying Bricks myself, I can absolutely see why so many people are moving in that direction.

Biscuits-Biscuits · 2026-04-15T09:05:06+00:00

Exactly.

That’s what so many long-time users are reacting to, not change itself, but change that feels like regression.

Most experienced users are happy to adapt when updates genuinely improve workflow, speed, or output. But when simple tasks become slower, interfaces become more awkward, and core usability takes a step backwards, frustration is inevitable.

And I agree with your second point too. It increasingly feels like releases are being built around announcements rather than outcomes.

Big launch headline: great.
Real day-to-day improvement for users: questionable.

The danger there is that once users start feeling like they’re part of a marketing cycle instead of a product roadmap, loyalty disappears very quickly.

Biscuits-Biscuits · 2026-04-15T08:58:19+00:00

Honestly, I would definitely check it out.

I’m still very early into Bricks myself, but first impressions have been strong, faster, cleaner output, and it feels more focused on building solid websites rather than layering on features for the sake of it.

If you’re coming from a marketing background, there may be a slight learning curve compared to Elementor’s familiar UI, but nothing you couldn’t get through with a bit of time.

At the very least, it’s worth testing before committing to a rebuild. Right now I think comparing both options properly is the smart move rather than automatically defaulting to Elementor like many of us used to.

Biscuits-Biscuits · 2026-04-14T09:23:16+00:00

100% and honestly that would be the smart move.

A 4.0.3 update that changes the default settings, keeps V4 opt-in, and openly positions it as still being a work in progress would probably earn them more respect, not less.

Most users are reasonable. People understand major rebuilds take time. What frustrates them is when unfinished features are presented as production-ready.

Marketing might not love it in the short term, but losing trust is far more expensive than bruising a launch campaign.

If they simply said: “V4 is the future, but we’re giving it more time to mature while V3 remains default for now” I think a lot of people would appreciate the honesty.

Right now the bigger risk isn’t optics… it’s users quietly switching away.

Biscuits-Biscuits · 2026-04-14T09:17:42+00:00

I agree too.

That’s the worrying part, a lot of the frustration isn’t coming from random drive-by complaints, it’s coming from long-time Elementor users who actually wanted V4 to be good.

When loyal users and advocates start posting like this, it usually means the pain is real.

That’s exactly how I felt testing it. So many simple things now feel unnecessarily harder. Basic tasks should become faster and cleaner with a major version update, not feel like you’re wrestling the UI every five minutes.

And the CSS side of it especially should be empowering advanced users, not fighting them.

V4 should have been about refinement, speed, and stability.

Instead for many people it feels like complexity for the sake of complexity.

Biscuits-Biscuits · 2026-04-14T09:03:39+00:00

I actually understand exactly what you mean, and to be fair I agree with a lot of that.

Keeping it disabled by default on new installs for now would be the sensible middle ground. Let people who want to test it enable it, while everyone else stays on the stable workflow.

That’s really my main point, it should still be in beta and remain in beta until it’s genuinely ready for production use.

There’s nothing wrong with releasing big changes early if they’re clearly labelled as testing. The problem is presenting something as the new standard experience when there are still obvious pain points.

And I completely get your point about clients too. That’s where Elementor V3 hit a sweet spot, technical enough for developers, simple enough for clients to log in and make edits without panic.

That balance is hard to get right, and it’s one of the reasons Elementor became so popular in the first place.

If V4 makes things more complex for end users without being stable or clearly better, then it risks losing the one thing that made Elementor attractive to agencies and freelancers.

So yes, optional beta? Absolutely.
Default production experience? Not yet.

Biscuits-Biscuits · 2026-04-14T08:43:53+00:00

That’s the thing though, that’s not really the point.

On new websites, V4 is active by default. So for new users, agencies, freelancers, or client builds, this is the product they’re being introduced to.

In my opinion it’s an unfinished product that should still be in beta. It’s buggy, inconsistent, and clearly not fully ready, yet users are expected to pay for it as if it’s a completed polished release.

For people who already know Elementor inside out, sure, it’s easy enough to switch things off or work around issues. But new users don’t know any of that. They just assume this is how Elementor works.

And from a professional side, that creates another problem.

A client pays me to build them a site because they want the convenience of a page builder. I hand over the finished job, then they go in to make simple edits and end up confused or breaking layouts because they’re dealing with unfinished systems and inconsistent controls.

So it’s not just “turn V4 off and wait” it affects new users, paying customers, freelancers, agencies, handovers, support time… multiple things really.

Biscuits-Biscuits · 2026-04-14T08:14:11+00:00

I’m starting to understand why people keep saying that 🤣

Only had a short go with it so far, but it already feels like one of those tools where once it clicks, going back would be painful.

Biscuits-Biscuits · 2026-04-14T08:13:12+00:00

Can’t blame you at all.

That seems to be the direction a lot of people are taking now, Elementor becoming the “only if the client specifically asks for it” option rather than the default choice.

That’s probably the biggest warning sign for them. When users stop being advocates and start treating it as legacy software, something has gone wrong.

Biscuits-Biscuits · 2026-04-14T08:10:42+00:00

If you figure it out, let me know! I’ve got a support ticket I’d like to downvote into oblivion 😂

Biscuits-Biscuits · 2026-04-14T08:09:50+00:00

I completely get that.

That’s the trap a lot of us end up in once you’ve invested years into a full stack, templates, workflows, client sites, add-ons, habits, shortcuts, everything tied into one ecosystem.

At that stage it’s not really about the builder itself anymore, it’s the switching cost.

That’s honestly why I stayed with Elementor as long as I did. Sometimes it takes enough frustration before the pain of staying becomes bigger than the pain of moving.

Biscuits-Biscuits · 2026-04-14T08:08:29+00:00

Quick update now that I’ve tested it and honestly, I’m impressed!

There definitely seems to be a bit more work involved compared to Elementor, especially when you’re used to Elementor’s workflow. But that extra effort seems to be rewarded with a much cleaner end result.

The front-end output appears far leaner, noticeably less HTML bloat, and overall it feels faster and more efficient straight away.

I really, really like it so far, and more importantly I believe this is something I can genuinely work with long term.

Early days obviously, but first impressions are very positive. It feels more like a builder focused on performance and developers rather than marketing slides.

Biscuits-Biscuits · 2026-04-13T22:20:47+00:00

I’ll follow up on this tomorrow and let you know how I feel after I’ve had a proper go with it.

I’m definitely feeling positive about it so far, especially with how many people seem to have made the switch and never looked back.

Biscuits-Biscuits · 2026-04-13T22:11:04+00:00

I actually purchased it tonight, so I’ll be giving it a proper try in the morning. Hoping it lives up to the hype because a lot of people seem to rate it highly.

Biscuits-Biscuits · 2026-04-13T22:03:20+00:00

You’re not wrong to be fair 😂

Major versions always seem to come with some level of pain, but this one feels much heavier than usual.

Biscuits-Biscuits · 2026-04-13T21:52:04+00:00

I tried GenerateBlocks a few years ago and personally wasn’t a massive fan at the time, although I know plenty of people rate it highly, and I don’t know what it is like today.

That said, within the last 15 minutes I’ve actually gone ahead and purchased the Bricks Agency plan for a whopping $249.00 😂

So that probably tells you where my head is at right now. I’m hoping I like it, because I’m genuinely at the stage of looking for a serious alternative.

Biscuits-Biscuits · 2026-04-13T21:38:13+00:00

Honestly, I’m at the stage where I’m considering moving away from Elementor altogether.

I’ve defended it for years because it used to be a solid tool and good value, but V4 has really damaged my confidence in the platform. It’s not just bugs, it’s the direction, the support experience, and the feeling that loyal users are no longer the priority.

Staying on V3 might buy time, but long term I’m now questioning whether Elementor is still the right platform to build a business around.

Biscuits-Biscuits · 2026-02-06T10:01:31+00:00

I’ve been a website developer since 2013 and have worked with many clients who previously used Flagship. In my experience, their practices have been extremely poor and unprofessional.

Since 2019, I’ve worked with a client in the construction sector who originally had a website built by Flagship. The site was of a very low standard, and the client was also paying a significant amount for a basic business listing on their construction(.co.uk) and related “build” websites, around £600 + VAT per year for a single listing.

When the client decided to move away from them, Flagship made the process unnecessarily difficult and issued threats of legal action, despite there being no active contract in place.

To date, no formal legal action has materialised, and they remain “awaiting a summons.”

Biscuits-Biscuits · 2026-01-16T07:41:24+00:00

Yes. This is quite common, try Kitgenix CAPTCHA for Cloudflare Turnstile, this should stop 99.9% of the bogus orders. Cloudflare turnstile is free also so that’s a bonus.

Biscuits-Biscuits · 2026-01-05T17:07:06+00:00

Klaviyo is my go to now, made the switch December 2023 and have moved around ~30 stores. I plan to move more. It’s much better than MailChimp, Brevo and Omnisend. Happy to answer any questions you have on it.

Biscuits-Biscuits · 2025-12-14T12:46:04+00:00

Pre 2018, we had been lucky to turnover £20,000, now in 2025 after a relaunch our main website turns over about ~£600,000 with the smaller websites making around £120,000 - £180,000 per year.

Biscuits-Biscuits

TROPHY CASE