When You Outgrow Wix (And When You Have Not)

An earlier version of this post argued that Wix was not good enough for a growing business, full stop. We have retitled it and rewritten it, because our own research made that argument indefensible.

The result we have to lead with

In our AI visibility study, we crawled 405 business websites, analyzed 368, and compared the fully rendered page against the raw HTML a non-rendering crawler receives. 92 of the 368 lost at least one answer-critical element, meaning body text, links, or contact details that appear on screen but never appear in the raw response.

Here are the counts by platform:

• Wix: 1 of 35
• Webflow: 1 of 15
• GoDaddy: 4 of 20
• Squarespace: 13 of 46
• WordPress: 37 of 139
• Other and custom builds: 34 of 107

Wix had exactly one affected site out of thirty-five. It was, alongside Webflow, the best-performing platform in the study. Custom builds were the worst group in practice, at 34 of 107.

We are an agency that builds custom React and Next.js sites. That result does not flatter us and we are publishing it anyway, because the alternative is writing a sales argument and calling it analysis.

Floor and ceiling

The wrong conclusion to draw is "so use Wix." That is the same overclaim as the original post, pointed the other way. Here is what the numbers actually support.

Wix has a high floor. It renders on its servers. Whatever is on the page is in the response, and that happens whether or not anyone at your company has ever heard the word crawler. It is not doing anything clever. It is doing the boring thing correctly, by default, for everyone, and the boring thing is what mattered. The ceiling arrives with the floor: you inherit the rendering path instead of choosing it, and you cannot go above what the platform does.

Custom has the lowest floor and the highest ceiling. A custom build sends whatever the developer decided it should send. A large share of them are client-rendered React applications, where the browser gets a nearly empty document and JavaScript assembles the page afterward. Crawlers that execute JavaScript see it. Crawlers that do not, including several that feed AI answer engines, see almost nothing. That is the worst outcome in our data. But a statically generated or server-rendered Next.js build puts every word in the raw HTML, and that is the best outcome available, because the rendering path was a decision rather than an inheritance. Our own site is custom Next.js and scores 100 out of 100 on DeepAudit and 10 out of 10 on AI readiness. No builder can be told to do that.

The custom bucket is a catch-all. Those 107 sites include hand-rolled static HTML and heavy single-page applications, filed under one label. It averages the best and worst architectures on the web together. That is why it looks bad, and it is why it cannot be read as a verdict on custom development.

The platform did not decide this. The rendering strategy did. Choose custom when someone is actually going to do the work, meaning server rendering or static generation, tested rather than assumed. Choose a builder when nobody will, because a high floor beats a ceiling you never climb.

Check yours before you argue with any of this. View the raw source of your homepage, not the browser inspector, the actual source, and search it for your headline and your phone number.

What Wix is genuinely good at

Speed to live. Hours, not weeks. For a new business that needs a presence now, that is worth real money, and paying an agency to spend six weeks reproducing it is a poor use of capital.

Non-developers can edit it. No ticket, no retainer, no waiting. This is the row that quietly decides most platform arguments.

Nothing to patch. No plugin updates, no PHP versions, no security advisories landing on your desk on a Friday.

Bundled infrastructure. Hosting, SSL, domain, analytics, in one bill.

It serves real HTML. As above. That is a technical compliment and it is earned.

Where Wix actually constrains you

These are real limits. We are stating them without inflating them into revenue loss.

Structured data. Wix generates some schema automatically. Adding custom JSON-LD for FAQ, HowTo, Product, or a detailed LocalBusiness graph is limited. Structured data does not earn rankings. It makes you eligible for certain result formats, and if you want that eligibility, you need control over the markup.

Markup and DOM control. You do not decide the heading hierarchy or element order. For a brochure site this is irrelevant. For a large content site with a deliberate architecture, it becomes a ceiling.

Page weight. Wix ships its platform runtime on every page, including code for features your page does not use. A hand-built static page ships less. You can measure this on your own site with a single Lighthouse run, and you should, because it is one of the few things in this article you can check in five minutes rather than take on faith.

Custom functionality. A pricing calculator, an unusual booking flow, a product configurator, a direct integration with your CRM, an AI chat wired into your own data. Velo gives you some room, inside a sandbox. A codebase gives you all of it.

Portability. You own your content, not your build. Leaving means rebuilding. Decide how much that matters before you start, not after.

The claims we removed

The original version of this post said Wix sites "consistently score 25 to 55" on Lighthouse Performance while custom sites score 90 to 100. We did not have platform-segmented performance data then and we do not have it now. Those ranges were not measured. They are gone.

It also said a slow Wix site means "you are losing the majority of your mobile visitors," and that most clients "see measurable improvements in rankings and lead volume within the first 60 days." We have not measured either of those. They are gone too.

What we have measured on performance is this: across the 292 sites in our small business study, 191 returned a valid mobile verdict and 185 of them failed at least one Lighthouse threshold. The median mobile Largest Contentful Paint was 10.5 seconds. Those are lab numbers from a purposive B2B prospect list, and the dataset does not record what platform any of those sites ran on. So it tells you the small business web is slow. It does not tell you Wix is why.

When it is actually time to leave Wix

Not because it is Wix. Leave when you hit a wall you can name.

You need functionality the platform cannot support, and cannot be made to support. You have measured a performance ceiling rather than assumed one. You need markup or schema control the platform will not give you. You are stacking paid apps to fill gaps that one build would close. You are building a product experience, not publishing a brochure.

And leave only if the replacement will be built properly. A custom site that is pre-rendered and tested is the best thing you can have. A custom site that renders in the browser is worse than the Wix site you left, and you will have paid for the privilege. If nobody is going to own that decision, staying on Wix is a legitimate engineering choice, and we will say so on a call.

What we did not measure

We have not measured conversion by platform. We have not measured rankings by platform. We have not measured revenue before and after a migration. We measured one thing, whether the content survives into raw HTML, and Wix won it as a group. We did not measure how many of the custom builds were pre-rendered, which is the variable that separates the top of that study from the bottom.

Anyone who tells you your platform choice determines your rankings is filling in a blank they did not measure either, including the version of us that wrote this post the first time.

Where to start

Run your site through our free SEO audit and read what it actually says. If it comes back healthy, you have your answer and it did not cost you anything. If it does not, book a consultation and we will tell you which problems are the platform and which are the content, because those are usually different problems with different price tags.