It is one of the first questions asked by slightly more technical online retailers: "yet another script to load, that's going to drag my site down". The concern is legitimate, and a slow site drives buyers away and penalises your search ranking. Here is the honest answer, without the marketing: how a well-designed withdrawal tag loads, what it actually does to your page, and how to check it for yourself.
The key point: asynchronous loading
Installation comes down to a single line, pasted into the <head> tag of your site:
<script async src="https://backtome.fr/widget.js" data-site="your-identifier"></script>
The word that matters is async. It changes everything. An asynchronous script never blocks the display of your page: the browser carries on building and displaying your content without waiting for the script to be downloaded or executed. Your product page appears, your checkout funnel works, and the withdrawal button shows up once the rest has loaded.
This is the opposite of a "blocking" script (without async or defer), which pauses the building of the page while it loads. A withdrawal tag that genuinely slowed you down would be a badly integrated tag, not an inevitable consequence of the obligation.
A single script, in native JavaScript
The second factor is what is inside the script. A lightweight widget is written in native ("vanilla") JavaScript, without bundling a heavy framework (no React, no jQuery, no library of several hundred kilobytes to download to your site). It is self-contained: it displays a floating button and a form, and forwards the request. Nothing more.
This is an important difference from certain third-party widgets (chats, marketing pop-ups, tracking tools) that drag bulky dependencies behind them. For withdrawal, you need none of that.
Served and cached by a CDN
Third factor: where the file comes from. The script is distributed from a CDN (content delivery network) and cached. In practice, it is not fully re-downloaded on every visit or every page: the visitor's browser and the intermediate servers keep a copy. The load on your own server is nil, because the file is not hosted on your site; it consumes neither your bandwidth nor your resources.
The real impact on your Core Web Vitals
Google's Core Web Vitals measure the loading experience. Let us look at each indicator:
- LCP (Largest Contentful Paint): the time it takes to display the largest visible element. Because the script is asynchronous, it does not delay the display of your main content. No impact expected.
- CLS (Cumulative Layout Shift): layout jumps. The withdrawal button is a floating element, overlaid on the page (fixed position), not inserted into the content flow. It therefore pushes nothing aside and causes no shift.
- INP (Interaction to Next Paint): responsiveness to clicks. The widget only runs when a visitor opens the form; it does not run in the background and does not monopolise the main thread.
In practice, the impact on your scores is negligible. A well-designed withdrawal tag sits in the same "weight" category as a small social media icon, a very long way from a marketing tool loaded with trackers.
What the script does, and what it does not do
Performance is also a matter of trust in what the code does. Let us be precise:
What it does: it displays a floating button and a withdrawal form over your page; it reads a site identifier to load the right configuration; it forwards a request so that it can be timestamped and archived.
What it does not do: it does not modify your code, your design or your catalogue; it does not track your customers for advertising purposes; it collects only the information needed to process a withdrawal. You stay in control: removing it means deleting one line.
Check it for yourself
Do not take my word for it; that is precisely the BackToMe philosophy. Two minutes are enough:
- Open your browser's developer tools ("Network" tab), reload your page and look at the size and loading time of the script: it loads in parallel, not in a blocking way.
- Run your URL through PageSpeed Insights (Google's free tool) before and after installation. Compare the scores: the difference should be imperceptible.
This is the right habit for any third-party script you add to your site, not just for withdrawal.
In summary
A withdrawal button does not slow down your site if it is loaded asynchronously, written in native JavaScript and served by a CDN, which is the case with a properly designed solution. The real value lies not in the button itself but in what sits behind it: the timestamped evidence that protects you the day a dispute arises. To go further on the other legitimate concerns (customer abuse, script security), see our page the withdrawal button protects you too, and for practical installation, the installation guide for your platform.
Founder of BackToMe
Art. L.221-21 · 19 June 2026
Ready to install the withdrawal feature?
Install the withdrawal button on your site in five minutes. 7-day free trial: 0 € today, 30-day money-back guarantee.
Start the free trial →