No-code has democratised website creation. Tools such as Webflow, Framer, Wix, Squarespace and Bubble have allowed thousands of freelancers and small organisations to get online without writing a line of code. In the right context, that is undeniably a success: for an MVP, a personal portfolio or a test landing page.
But when a serious Swiss SME (with growth targets, real local competition and performance expectations) builds its digital strategy on a no-code platform, it inevitably hits ceilings. Ceilings on performance, SEO, customisation and cost. This article documents them in detail, with real data.
What no-code promises, and what it actually delivers
The initial promise is real
Let us start by being honest: no-code tools have come a long way. Webflow in particular generates clean HTML/CSS, supports advanced animations and offers a built-in CMS. Framer provides smooth interactions and a Figma-inspired interface. These tools are not toys.
For some use cases, 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 problem arises when these tools are used for projects beyond what they were designed for. And Swiss SMEs, with their competitive markets and demanding customers, almost always go beyond that scope.
The false savings of no-code
The economic promise of no-code rests on removing the developer. In reality, here are the actual 3-year costs of a professional website on a no-code platform:
Above all: you do not own your website. Your content, your design and your CMS database live on the servers of an American company. If Webflow raises its prices by 30 % (which it already did in 2023), you either pay or migrate, losing all the work invested in the platform. If Framer is acquired or shuts down, your options drop to zero.
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 to rank websites. Since the Page Experience update (2021), a site that performs poorly on these metrics is penalised in search results.
Here are the median scores observed on no-code sites in production (data from real audits and Google's CrUX dataset, 2024):
Most no-code platforms fail to reach Google's "Good" thresholds on at least one metric. Webflow does better than Wix, but remains far from what custom code can achieve.
Why these ceilings are structural
No-code platforms generate code from a graphical interface. This process inevitably produces sub-optimal code:
Bloated CSS: the visual editor generates CSS rules for every property of every element, even those set to default values. A simple component in Webflow can generate 80 lines of CSS where a developer would write 15. Every visitor has to download that unnecessary CSS.
Platform JavaScript: Webflow loads its JS runtime (webflow.js) on every page (around 150 KB minified). This bundle handles interactions, animations and the CMS. It cannot be tree-shaken: even if you use only 10 % of its features, you load 100 % of the bundle.
No control over the <head>: no-code tools automatically generate the <link> and <script> tags in the <head>. You cannot finely control preload, prefetch or the loading order of critical resources. These optimisations often account for 30 to 50 % of the performance gain on a well-coded site.
Images not fully optimised: while Webflow and Framer serve images in WebP, they do not systematically generate every size needed for each viewport. On mobile, a user may download an image twice as large as necessary.
No real Server-Side Rendering: Webflow generates static HTML, which is good. So does Framer. But dynamic features (search, filters, advanced forms) require client-side JavaScript, often through third-party integrations that add extra scripts.
The concrete impact on SEO
A Lighthouse score of 58 versus 94 is more than a number. According to a Portent study (2023), a site that loads in 2.4 seconds converts 2.5× less than a site that loads in 0.9 seconds. For an SME investing in SEO, that is a structural handicap that even the best content in the world cannot make up for.
According to Search Engine Journal, sites that reach the "Good" thresholds on all Core Web Vitals receive on average 24 % more organic clicks than sites below those thresholds, at equal ranking. In other words, even if your no-code site ranks well for a query, it converts fewer clicks, because Google shows users a performance indicator and they choose the faster site.
Technical SEO: the structural limits of no-code
What you cannot control on Webflow or Framer
Technical SEO is the invisible foundation of your organic visibility. This is where no-code platforms reveal their most frustrating limitations.
JavaScript rendering and indexing: Framer is a React-based site builder. By default, rendering happens client-side. Although Framer has improved on SSR (Server-Side Rendering), fine control over rendering (deciding which parts are rendered on the server versus the client) is not available without code.
Structured Data (JSON-LD): structured data allows Google to display rich snippets (stars, prices, FAQs, events) in search results. On Webflow, adding JSON-LD requires a workaround via 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: managing complex redirects (regex patterns, conditional redirects, redirect chains) is limited on most no-code platforms. In Next.js, it takes a few lines in next.config.ts.
hreflang tags for multilingual sites: a Swiss SME targeting French-, German- and English-speaking customers needs a multilingual site with correctly implemented hreflang tags. Webflow now supports multiple languages, but its automatic hreflang tags do not cover every use case, and managing multilingual slugs is rigid.
Dynamic sitemap generation: in Next.js, generating an XML sitemap that dynamically includes every page, blog post and shop URL takes 20 lines of code and rebuilds with every deployment. On no-code platforms, the sitemap is either generated automatically (with no control) or does not exist.
Dynamic Open Graph tags and Twitter Cards: sharing a blog post on LinkedIn or Twitter with the right title, image and description requires dynamic OG tags per page. In Next.js, the Metadata API handles this natively. On Webflow, it is configurable but subject to 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 that sends data to your CRM, an interactive map, a product configurator, a client area), you face a choice:
- Use a native integration (often limited)
- Go through Zapier / Make (extra cost, latency, fragility)
- Embed a third-party script (extra weight, GDPR / Swiss FADP (revFADP) compliance to manage)
- Discover that it simply cannot be done on the platform
With custom-built code, every integration is written exactly as needed: no more, no less. No Zapier, no fragile webhooks, no third-party scripts outside your control.
Customisation: the invisible wall of no-code
The designs that "can't be done"
Every no-code tool has its own visual vocabulary: implicit constraints that make all Webflow sites "look a bit alike". This is no accident: the tool imposes its own way of thinking about layout, animation and interaction.
A few concrete examples of effects or behaviours that are impossible (or extremely expensive) to achieve in no-code:
Advanced GSAP animations: GSAP (GreenSock Animation Platform) is the most powerful JavaScript animation library on the web. It enables complex timelines, SVG morphing effects and pixel-perfect scroll-linked animations. On Webflow, you can use GSAP through embeds, but you lose access to the visual editor for those elements, and debugging JavaScript inside a Webflow embed is a painful experience.
Smooth page transitions: a transition between two pages (fade, slide, element morphing) requires control over the navigation lifecycle. This is native in Next.js with the View Transitions API or GSAP animations tied to the router. On any no-code platform, it is a complicated hack.
Canvas and WebGL: sites using Three.js, React Three Fiber or canvas animations to create immersive experiences are simply impossible on standard no-code platforms.
Complex conditional logic: showing different content depending on the time of day, the user's location, their history or their tier in a loyalty programme: all of this requires code. No-code tools can simulate simple conditional logic, but quickly reach their limits.
Mobile performance: Webflow animations use Webflow's proprietary interaction engine. On mobile (patchy 4G, limited processors), these animations can cause stuttering (jank) that you cannot debug or optimise without access to the source code.
The tyranny of the template
Even Webflow, for all its flexibility, imposes constraints on component structure. A slider, a navigation menu, an accordion: they work according to Webflow's logic, not yours. You can customise the appearance, but rarely the fundamental behaviour.
With React and Next.js, every component is a function. An accordion behaves exactly the way you define it: it can have a unique opening animation, complex state logic, integration with your analytics and flawless accessibility. Nothing is imposed.
Scalability: where no-code really cracks
When traffic climbs
A press campaign, a viral post, a traffic spike after an event: your website has to hold up. No-code platforms host your sites on their own infrastructure. Webflow guarantees 99.99 % uptime on its CDN for static sites, which is good. But when their infrastructure is in trouble (which does happen, Webflow included), your site is in trouble too.
A Next.js site deployed on Vercel, Netlify or Cloudflare Pages runs on a global CDN infrastructure with contractual guarantees. In static mode, it is practically indestructible under traffic: 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: 2,000 items per collection (Business plan), 10,000 (Enterprise plan at CHF 235/month)
- 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: volumes like these exceed the standard plans of no-code platforms or force 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 is yours, stored wherever you want, and scales without changing plans.
The real total cost over 5 years
Here is the full calculation, including every cost for a professional SME website over 5 years:
And most importantly: after 5 years, the custom-built Next.js site belongs entirely to you. It can be hosted anywhere, maintained by any React developer and extended without limits. The Webflow site depends on the survival of an American company and on its pricing decisions.
When no-code is still the right choice
In the interest of intellectual honesty, here are the cases where no-code still 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 is smarter than waiting 2 months for a custom build.
Very simple sites with no competitive SEO ambitions: a local association, an artist, a freelancer in a low-competition sector. If the site does not need to fight for Google rankings, the SEO limitations of no-code have little impact.
An in-house team with Webflow skills: if you have an in-house designer who knows Webflow inside out and can maintain the site themselves, the economics change.
In every other case (SMEs with growth targets, competitive sectors, a need for customisation, real SEO ambitions), custom-built code is the rational investment.
What INFUSE offers compared with 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".
The result: you own your website. The source code is delivered in a Git repository that belongs to you. The site can be hosted with any provider, including Infomaniak in Switzerland if data sovereignty is a requirement. Performance is optimised at the source, not patched together with plugins.
If your current site runs on Webflow or Framer and you are starting to feel the limits (mediocre Lighthouse scores, a design you cannot evolve the way you imagine, rising subscription fees), now is the right time to talk.