No-code has opened up website creation to everyone. Webflow, Framer, Wix, Squarespace and Bubble have let thousands of freelancers and small organisations get online without writing code. In some contexts, that works well: an MVP, a personal portfolio, a test landing page.
Things change when a Swiss SME (growth targets, real local competition, performance expectations) builds its whole digital strategy on a no-code platform. Sooner or later it runs into ceilings: performance, SEO, customisation and cost. This article goes through them, with figures.
What no-code promises, and what it delivers
The initial promise holds up
To be fair, no-code tools have improved a lot. Webflow generates clean HTML/CSS, supports advanced animations and includes a CMS. Framer offers smooth interactions and an interface close to Figma. These are not toys.
For some uses, they are a perfect fit:
- A freelancer who wants an online portfolio in 48 hours
- A start-up validating a concept with a landing page
- A non-profit on a tight budget that needs a basic presence
- A simple e-commerce shop in a low-competition niche
The trouble starts when they are used for projects beyond what they were designed for. Swiss SMEs, with competitive markets and demanding customers, nearly always fall outside that scope.
The false savings of no-code
The financial case for no-code is that you do without a developer. Yet over 3 years, a professional website on a no-code platform adds up several costs:
- a yearly subscription, paid for as long as the site exists, at the price set by the vendor
- paid add-ons if you need e-commerce
- a capped CMS that pushes you to a higher plan as your content grows
- a costly migration the day you leave the platform, because most of the site has to be rebuilt
Above all, you do not own your website. Your content, design and CMS database sit on the servers of an American company. If Webflow raises its prices, you either pay or migrate, and lose the work invested in the platform. If Framer is acquired or shuts down, you are left with no options.
Core Web Vitals: the technical ceiling of no-code
The Google metrics no-code struggles to hit
Core Web Vitals are the performance metrics Google uses in its rankings. Since the Page Experience update (2021), a site that does poorly on them is penalised in search results.
No-code platforms often miss Google's "Good" threshold on at least one metric, especially on mobile. Webflow does better than Wix, but stays well short of what custom code achieves, for reasons that come from the platform itself.
Why these ceilings are structural
A no-code platform generates code from a graphical interface. That code is bound to be less efficient:
Bloated CSS: the visual editor writes CSS rules for every property of every element, default values included. A simple component in Webflow can produce far more CSS than a developer would write. Every visitor downloads that extra CSS.
Platform JavaScript: Webflow loads its JS runtime (webflow.js) on every page. This bundle handles interactions, animations and the CMS. It cannot be tree-shaken: even if you use only a small part of its features, you still load the whole bundle.
No control over the <head>: the <link> and <script> tags in the <head> are generated automatically. You cannot fine-tune preload, prefetch or the loading order of critical resources. On a well-coded site, these settings weigh heavily in the performance gain.
Badly sized images: Webflow and Framer do serve WebP, but they do not always generate every size needed for each viewport. On mobile, a visitor may download an image much larger than their screen.
No real Server-Side Rendering: Webflow generates static HTML, which is good, and so does Framer. But dynamic features (search, filters, advanced forms) rely on client-side JavaScript, often through third-party integrations that add their own scripts.
The concrete effect on SEO
A slow site is not just a technical problem. For an SME investing in SEO, it is a handicap that even excellent content struggles to make up for: Google includes page experience in its rankings, and a visitor who has to wait leaves.
Technical SEO: the limits of no-code
What you cannot control on Webflow or Framer
Technical SEO is the invisible base of your organic visibility. It is also where no-code platforms show their most frustrating limits.
JavaScript rendering and indexing: Framer is a React-based site builder that renders client-side by default. Framer has improved on SSR (Server-Side Rendering), but choosing precisely what is rendered on the server or the client is still impossible without code.
Structured data (JSON-LD): it lets Google display rich snippets (stars, prices, FAQs, events) in search results. On Webflow, you have to use an HTML embed field: it works, but it is fragile, untyped and hard to maintain. On Framer, it is not possible natively.
Advanced 301 redirects: complex redirects (regex patterns, conditional redirects, redirect chains) are limited on most no-code platforms. In Next.js, a few lines in next.config.ts are enough.
hreflang tags for multilingual sites: a Swiss SME targeting French-, German- and English-speaking customers needs a multilingual site with correct hreflang tags. Webflow now supports multiple languages, but its automatic hreflang tags do not cover every case and per-language slugs are rigid.
Dynamic sitemaps: in Next.js, an XML sitemap covering every page, blog post and shop URL takes 20 lines of code and rebuilds with each deployment. On no-code platforms, the sitemap is either automatic (with no control) or missing.
Dynamic Open Graph tags and Twitter Cards: to share a post on LinkedIn or Twitter with the right title, image and description, each page needs its own OG tags. In Next.js, the Metadata API handles this natively. On Webflow, it is configurable within the limits of its CMS. On Framer, it is rudimentary.
The third-party integration problem
As soon as your no-code site needs something non-standard (a form linked to your CRM, an interactive map, a product configurator, a client area), you have four options:
- Use a native integration (often limited)
- Go through Zapier / Make (extra cost, latency, fragility)
- Add a third-party script (extra weight, GDPR / Swiss FADP (revFADP) compliance to manage)
- Find out the platform cannot do it
With custom code, each integration is written for the exact need. No Zapier, no fragile webhooks, no third-party scripts outside your control.
Customisation: the limit you do not see at first
The designs that "can't be done"
Every no-code tool has its own visual vocabulary, with implicit constraints. That is why Webflow sites "look a bit alike": the tool imposes its own way of thinking about layout, animation and interaction.
A few effects or behaviours that are impossible (or very expensive) in no-code:
Advanced GSAP animations: GSAP (GreenSock Animation Platform) is the most powerful JavaScript animation library on the web. It handles complex timelines, SVG morphing and pixel-precise scroll animations. On Webflow, you can use it through embeds, but you then lose the visual editor for those elements, and debugging JavaScript inside a Webflow embed is painful.
Smooth page transitions: a transition between two pages (fade, slide, element morphing) requires control over the navigation lifecycle. In Next.js, this is native with the View Transitions API or GSAP animations tied to the router. On a no-code platform, it is a complicated workaround.
Canvas and WebGL: immersive experiences built with Three.js, React Three Fiber or canvas are impossible on standard no-code platforms.
Complex conditional logic: showing different content depending on the time, the visitor's location, their history or their loyalty tier requires code. No-code tools can mimic simple conditional logic, then soon reach their limits.
Mobile performance: Webflow animations run on Webflow's proprietary interaction engine. On mobile (patchy 4G, limited processors), they can stutter (jank), and without access to the source code you can neither debug nor optimise them.
The template constraint
Even Webflow, flexible as it is, imposes a structure on components. A slider, a menu or an accordion works according to Webflow's logic, not yours. You can change the look, rarely the underlying behaviour.
With React and Next.js, every component is a function. An accordion does exactly what you define: its own opening animation, complex state logic, a link to your analytics, full accessibility. Nothing is imposed.
Scalability: where no-code gives way
When traffic climbs
A press campaign, a viral post, a spike after an event: your site has to hold up. No-code platforms host sites on their own infrastructure. For static sites, Webflow's CDN is solid, which is decent. But when their infrastructure has a problem (it happens, Webflow included), so does your site.
A Next.js site deployed on Vercel, Netlify or Cloudflare Pages runs on a global CDN. In static mode, no traffic spike brings it down: there is no server to overload, and the HTML is served from the CDN node closest to each visitor.
When content grows
Most no-code platforms limit the volume of content:
- Webflow CMS: items per collection capped depending on the plan
- Framer CMS: limited depending on the plan
- Wix: storage and bandwidth limits
A blog that stays active for 5 years, a shop with 500 products, a training catalogue: these volumes exceed the standard plans or push you onto expensive enterprise plans.
With Next.js and a headless CMS (Sanity, Contentful, Directus) or Markdown files, there is no content limit. Your database belongs to you, is stored wherever you choose and grows without a plan change.
What you pay over 5 years
Here is our estimate for a professional SME website over 5 years:
After 5 years, the custom-built Next.js site belongs entirely to you. You can host it anywhere, any React developer can maintain it, and it can evolve without limits. The Webflow site depends on the survival and pricing policy of an American company, and five years of subscription come on top of the amounts above.
When no-code is still the right choice
To be fair, here are the cases where no-code makes sense:
MVP and validation: you are launching a new service and want to test the market quickly on a minimal budget. A Webflow or Framer site in 2 weeks beats waiting 2 months for a custom build.
Very simple sites with no competitive SEO stakes: a local association, an artist, a freelancer in a quiet sector. If the site does not need to fight for Google rankings, the SEO limits of no-code matter little.
An in-house team that knows Webflow: if an in-house designer knows Webflow well and can maintain the site alone, the numbers change.
In other cases (an SME aiming to grow, a competitive sector, a need for customisation, serious SEO goals), custom code is the sounder investment.
How INFUSE approaches no-code platforms
INFUSE does not build sites on third-party platforms. No Webflow, no Framer, no Wix. Every project is developed in Next.js 16 with React 19, TypeScript, GSAP and Tailwind CSS v4: open-source technologies you do not have to "rent".
In practice, the site is yours. The source code is delivered in a Git repository that belongs to you. It can be hosted with any provider, including Infomaniak in Switzerland if data sovereignty matters to you. Performance is built into the code, not patched with plugins.
Frequently asked questions
Is no-code enough for a Swiss SME?
For an MVP, a very simple site with no competitive SEO stakes, or an in-house team that knows Webflow, yes. For an SME aiming to grow in a competitive sector, the limits on performance, technical SEO and customisation show up quickly.
Is a no-code site cheaper than a custom-built one?
At the start, yes. Over 5 years, the gap narrows: the subscription, paid integrations and the risk of a forced migration add up every year, while a custom-built site belongs to you and carries no platform subscription.
Can you add JSON-LD structured data on Webflow or Framer?
On Webflow, yes, through an HTML embed field, but it is fragile and hard to maintain. On Framer, it is not possible natively.
If your current site runs on Webflow or Framer and you are feeling the limits (mediocre Lighthouse scores, a design that cannot evolve the way you want, rising subscriptions), now is a good time to talk.