Duda Doubles Down on eCommerce with its Recent Acquisition of Snipcart

September 1, 2021
0 minute read

As you may have heard, we have finalized the acquisition of Snipcart, an eCommerce solution that allows online businesses to add a fully functional shopping cart to any website. The work to integrate the two platforms has already begun and is expected to be completed early next year. 


This acquisition means that Duda will soon be able offer improved
eCommerce solutions to web professionals, digital agencies and SaaS platforms who serve SMB clients. To help understand insights into the details of the acquisition from a more personal perspective, we sat Duda’s Itai Sadan and Snipcart’s Francois Lanthier Nadeau in the CEO hot seat.


We’ll discuss how the acquisition reflects what the overall process entailed for both teams, the new platform capabilities being developed post-purchase, and how the acquisition reflects major ongoing eCommerce trends.

What The Process Entailed For The Teams Involved

The move to acquire Snipcart was a top priority for us and happened in the midst of tremendous growth for the company. According to Sadan, this move was conducted because Duda’s team recognized that the existing eCommerce solution was not flexible or modular enough to satisfy our existing customer needs. 

Snipcart's experienced team of developers has built a reputation for providing flexible, modern cart designs. In acquiring Snipcart, we have not just gained superior technology to help our customers scale their online businesses even faster, but we’ve also brought in a team of industry leaders who understand the ins-and-outs of eCommerce integration. 

Both of these factors mean that Duda is now in an even stronger position to offer advanced shopping cart capabilities to customers in an era where the eCommerce market is expected to expand to $6.3 trillion within the next three years. 

“The growth we have seen in the eCommerce market is driven by the global pandemic causing a shift from offline to online sales,” says Sadan. “Duda has also seen the demand for its existing eCommerce product increasing.”

This should come as no surprise when you consider that Duda has seen a massive 256% increase in the number of eCommerce sites built with its platform. To date, over 14,000,000 websites have been built with Duda.

As to why Duda decided to go with Snipcart, Sadan elaborated: “we wanted to provide a more beautiful and modern shopping experience. The options we had were either to build it ourselves, which would have taken a long time, or shorten the path by acquiring a company that has already built what we were looking for.”

And as to why Snipcart decided to sell to Duda rather than scale themselves up independently, Lanthier Nadeau says it came down to realizing they had the opportunity to get its platform into the hands of many more users with a company that shared their values and would make integration a feasible challenge.

“After a couple of exchanges between teams, we knew where we stood,” said Lanthier Nadeau. “Both sides had mature tech stacks, and knew what would need refactoring, new features, or both. The integration would come with some challenges, but nothing excessive.”

Lanthier Lanthier Nadeau also recognized that Snipcart becoming a part of Duda versus scaling on its own would actually enable the company to develop its platform even further, leading to a “net positive” for the careers of Snipcart’s team members. 

Joining Duda would also “accelerate the development of some key features we had wanted to ship for a long time,” Lanthier Nadeau said, while adding, “We’d get to scale our systems to handle transaction volumes orders of magnitude higher than our current ones.”

Duda conducted a very thorough research of the ecommerce platform market. We had conversations with the teams of multiple organizations before realizing that Snipcart would be the perfect fit for what Duda and its customers needed.

What we liked about Snipcart was that with a relatively small and talented team they had built a state-of-the-art eCommerce platform used by thousands of customers worldwide,” says Sadan. “Their focus on flexibility and modern eCommerce store design is very much aligned with Duda’s product vision of providing its customers with beautiful and modular eCommerce solutions.”

This was Duda’s first acquisition, and a new experience for Sadan. The acquisition was made more difficult due to problems compounded by the pandemic. 

“I have raised a lot of money from investors which had its similarities, but buying a company was a whole different ball game,” says Sadan. “In addition, we had to do it all remotely due to the Covid Pandemic which made it even more difficult. It was roughly four months of discussions and another two months of due diligence.”

In the end though, it’s clear that the trials of the negotiations were well worth it, the teams are now heads down working on the integration between the two platforms with great progress being made thanks to their collaboration. Both teams have no doubt that once integration will be completed customers will greatly benefit from the joint solution.

Post-Purchase Platform Capabilities 


The burning question is how Duda’s platform capabilities will expand and become more aligned with the needs of our customers and the future direction of eCommerce, as a result of this move. 

Already, Duda has established itself as one of the foremost website builders on the market today. Our platform lowers the average website build time by 50% to 75%, making it one of the fastest web builders available. 

Much faster build times became a standard for duda’s clients thanks to the platform’s low-code/no-code capabilities and automated side building features, amongst other dynamic features. Once Snipcart’s technology is fully integrated into duda’s platform, site users will be able to access more features that they’ve always wanted. 

What are some of these features? 

“I think the main one is that Snipcart makes it very easy to make any content shoppable and this will allow Duda to offer a very flexible eCommerce solution,” says duda’s CTO Amir Glatt. “We will be able to offer both the classic eCommerce catalog side by side with other scenarios such as charge a subscription to access site content, the ability to integrate payments to custom widget built in our widget builder such as a custom form that accepts payments or make any external inventory shoppable via Duda’s storefront. Another thing which our customers will love is the ability to customize the shopping cart and add new components to it.”

But it’s not just Duda’s customers who will benefit from the merger. Snipcart’s customers stand to gain equally as well. According to Lanthier Nadeau, “Having Duda's support and resources will help us scale the dev team, and increase velocity for Snipcart's core product.”

As a result of integrating into Duda, Snipcart customers will now have access to new features that include:

  • Shipping fulfillment integrations 
  • Improved marketplace support 
  • Improved social selling support 
  • User-friendly store customization tools 
  • Client collaboration and billing tools 
  • A faster site editor 
  • White labelling of CMS functions 

A Strategic Move Reflecting Major ecommerce Trends


With the above features in mind, it can be said that arguably the biggest benefit the Duda and Snipcart integration will provide everyday small business owners is the ability to gain more control over their online stores versus ceding much of that control to third parties. 

“Meaning businesses serious about online commerce will realize that depending too much on third party channels and platforms can pose a significant risk,” Lanthier Nadeau points out. “If all of your eCommerce traffic comes from Instagram or Facebook, you're always at the mercy of their algo updates or ad price hikes. Same thing with Google updates if you're relying purely on paid or organic traffic. I think all of the above are great channels to generate traction at the margins of your business, but you really want to push people towards channels you have complete control over and don’t need to pay in order to interact with them: your website, your email subscribers, your store, and your contact list.”

Lanthier Nadeau argues that this reflects an overarching trend of ‘decentralization and automation’ in the digital economy. SMB owners in particular have been put on their toes as a result of the pandemic, since record numbers of physical stores have been closed and digital sales channels have subsequently become even more important. For some of these SMB owners, turning to eCommerce has now become their primary source of income when before they had not yet fully invested into eCommerce platforms as much as they should have.

“Many other SMBs that had not yet invested in eCommerce scrambled to go transactional online and catch up with competitors and unpaid bills,” Lanthier Nadeau says. “And sadly, that pandemic fear of things locking down again is here to stay for a few years.”

In other words, the current trend isn’t likely to go away. This bodes well for Duda and Snipcart. As has been discussed, Duda already offers some of the fastest web building times to its customers, who include web professionals, digital agencies and SaaS platforms who offer websites to SMBs. Thanks to the acquisition of Snipcart, it will now become an equally flexible eCommerce solution. 

A Note From the Editor


Duda’s acquisition of Snipcart represents one of the most significant moves in the eCommerce sphere. Duda plans to invest heavily into further developing the features of Snipcart’s platform and providing the Snipcart team with all the resources they need. It’s worth noting, however, that the Snipcart platform will continue to be offered independently to customers. 

For Duda’s and Snipcart’s customer base, the acquisition means gaining greater control over and having a much easier time building eCommerce stores. And at the same time, making the duda platform a more appealing choice to those individuals and companies who build sites for SMBs.


Did you find this article interesting?


Thanks for the feedback!
By Shawn Davis April 16, 2026
Website builder analysed 69M AI crawler visits across over 850,000 websites in February 2026 to determine key trends and characteristics that increase local AEO
By Shawn Davis April 1, 2026
Core Web Vitals aren't new, Google introduced them in 2020 and made them a ranking factor in 2021. But the questions keep coming, because the metrics keep changing and the stakes keep rising. Reddit's SEO communities were still debating their impact as recently as January 2026, and for good reason: most agencies still don't have a clear, repeatable way to measure, diagnose, and fix them for clients. This guide cuts through the noise. Here's what Core Web Vitals actually measure, what good scores look like today, and how to improve them—without needing a dedicated performance engineer on every project. What Core Web Vitals measure Google evaluates three user experience signals to determine whether a page feels fast, stable, and responsive: Largest Contentful Paint (LCP) measures how long it takes for the biggest visible element on a page — usually a hero image or headline — to load. Google considers anything under 2.5 seconds good. Above 4 seconds is poor. Interaction to Next Paint (INP) replaced First Input Delay (FID) in March 2024. Where FID measures the delay before a user's first click is registered, INP tracks the full responsiveness of every interaction across the page session. A good INP score is under 200 milliseconds. Cumulative Layout Shift (CLS) measures visual stability — how much page elements unexpectedly move while content loads. A score below 0.1 is good. Higher scores signal that images, ads, or embeds are pushing content around after load, which frustrates users and tanks conversions. These three metrics are a subset of Google's broader Page Experience signals, which also include HTTPS, safe browsing, and mobile usability. Core Web Vitals are the ones you can most directly control and improve. Why your clients' scores may still be poor Core Web Vitals scores vary dramatically by platform, hosting, and how a site was built. Some of the most common culprits agencies encounter: Heavy above-the-fold content . A homepage with an autoplay video, a full-width image slider, and a chat widget loading simultaneously will fail LCP every time. The browser has to resolve all of those resources before it can paint the largest element. Unstable image dimensions . When an image loads without defined width and height attributes, the browser doesn't reserve space for it. It renders the surrounding text, then jumps it down when the image appears. That jump is CLS. Third-party scripts blocking the main thread . Analytics pixels, ad tags, and live chat tools run on the browser's main thread. When they stack up, every click and tap has to wait in line — driving INP scores up. A single slow third-party script can push an otherwise clean site into "needs improvement" territory. Too many web fonts . Each font family and weight is a separate network request. A page loading four font files before rendering any text will fail LCP, especially on mobile connections. Unoptimized images . JPEGs and PNGs served at full resolution, without compression or modern formats like WebP or AVIF, add unnecessary weight to every page load. How to measure them accurately There are two types of Core Web Vitals data you should be looking at for every client: Lab data comes from tools like Google PageSpeed Insights, Lighthouse, and WebPageTest. It simulates page loads in controlled conditions. Lab data is useful for diagnosing specific issues and testing fixes before you deploy them. Field data (also called Real User Monitoring, or RUM) comes from actual users visiting the site. Google collects this through the Chrome User Experience Report (CrUX) and surfaces it in Search Console and PageSpeed Insights. Field data is what Google actually uses as a ranking signal — and it often looks worse than lab data because it reflects real-world device and connection variability. If your client's site has enough traffic, you'll see field data in Search Console under Core Web Vitals. This is your baseline. Lab data helps you understand why the scores are what they are. For clients with low traffic who don't have enough field data to appear in CrUX, you'll be working primarily with lab scores. Set that expectation early so clients understand that improvements may not immediately show up in Search Console. Practical fixes that move the needle Fix LCP: get the hero image loading first The single most effective LCP improvement is adding fetchpriority="high" to the hero image tag. This tells the browser to prioritize that resource over everything else. If you're using a background CSS image for the hero, switch it to anelement — background images aren't discoverable by the browser's preload scanner. Also check whether your hosting serves images through a CDN with caching. Edge delivery dramatically reduces the time-to-first-byte, which feeds directly into LCP. Fix CLS: define dimensions for every media element Every image, video, and ad slot on the page needs explicit width and height attributes in the HTML. If you're using responsive CSS, you can still define the aspect ratio with aspect-ratio in CSS while leaving the actual size fluid. The key is giving the browser enough information to reserve space before the asset loads. Avoid inserting content above existing content after page load. This is common with cookie banners, sticky headers that change height, and dynamically loaded ad units. If you need to show these, anchor them to fixed positions so they don't push content around. Fix INP: reduce what's competing for the main thread Audit third-party scripts and defer or remove anything that isn't essential. Tools like WebPageTest's waterfall view or Chrome DevTools Performance panel show you exactly which scripts are blocking the main thread and for how long. Load chat widgets, analytics, and ad tags asynchronously and after the page's critical path has resolved. For most clients, moving non-essential scripts to load after the DOMContentLoaded event is a meaningful INP improvement with no visible impact on the user experience. For websites with heavy JavaScript — particularly those built on frameworks with large client-side bundles — consider breaking up long tasks into smaller chunks using the browser's Scheduler API or simply splitting components so the main thread isn't locked for more than 50 milliseconds at a stretch. What platforms handle automatically One of the practical advantages of building on a platform optimized for performance is that many of these fixes are applied by default. Duda, for example, automatically serves WebP images, lazy loads below-the-fold content, minifies CSS, and uses efficient cache policies for static assets. As of May 2025, 82% of sites built on Duda pass all three Core Web Vitals metrics — the highest recorded pass rate among major website platforms. That baseline matters when you're managing dozens or hundreds of client sites. It means you're starting each project close to or at a passing score, rather than diagnosing and patching a broken foundation. How much do Core Web Vitals actually affect rankings? Honestly, they're a tiebreaker — not a primary signal. Google has been clear that content quality and relevance still dominate ranking decisions. A well-optimized site with thin, irrelevant content won't outrank a content-rich competitor just because its CLS is 0.05. What Core Web Vitals do affect is the user experience that supports those rankings. Pages with poor LCP scores have measurably higher bounce rates. Sites with high CLS lose users mid-session. Those behavioral signals — time on page, return visits, conversions — are things search engines can observe and incorporate. The practical argument for fixing Core Web Vitals isn't just "because Google said so." It's that faster, more stable pages convert better. Every second of LCP improvement can reduce bounce rates by 15–20% depending on the industry and device mix. For client sites that monetize through leads or eCommerce, that's a revenue argument, not just an SEO argument. A repeatable process for agencies Audit every new site before launch. Run PageSpeed Insights and record LCP, INP, and CLS scores for both mobile and desktop. Flag anything in the "needs improvement" or "poor" range before the client sees the live site. Check Search Console monthly for existing clients. The Core Web Vitals report surfaces issues as they appear in field data. Catching a regression early — before it compounds — is significantly easier than explaining a traffic drop after the fact. Document what you've improved. Clients rarely see Core Web Vitals scores on their own. A monthly one-page performance summary showing before/after scores builds credibility and makes your technical work visible. Prioritize mobile. Google uses mobile-first indexing, and field data shows that mobile CWV scores are almost always worse than desktop. If you only have time to optimize one version, do mobile first. Core Web Vitals aren't a one-time fix. Platforms change, new scripts get added, campaigns bring in new widgets. Build the audit into your workflow and treat it like any other ongoing deliverable, and you'll stay ahead of the issues before they affect your clients' rankings. Duda's platform is built with Core Web Vitals performance in mind. Explore how it handles image optimization, script management, and site speed automatically — so your team spends less time debugging and more time building.
By Ilana Brudo March 31, 2026
Vertical SaaS must transition from tools to an AI-powered Vertical Operating System (vOS). Learn to leverage context, end tech sprawl, and maximize retention.
Show More

Latest posts