Do you think we're overweight?
Try our light SDK and gain SEO performance points!
By default, we offer an optimized SDK regardless of the browser used. Fully delivered by an ultra-performant CDN, our widgets always load quickly and never impact your website's loading time.
Still, many of you closely monitor your page weight. Indeed, Google is increasingly prioritizing website speed in its algorithm that ranks pages in its search engine.
In this context and to allow you to improve your SEO score, we have deployed a significantly lighter SDK:
🤘 161 Kb instead of 186 Kb
Want to put us on a diet?
We explain everything to you!
When should you keep the standard SDK at 150 Kb?
If you chose Axeptio, it's probably for our polished UX! Unlike other ultra-light solutions that chose to disfigure sites with monochrome panels on page load, we preferred to opt for smoothness, style, and interactivity. And to offer the same experience to all users, regardless of the browser version used, we use polyfills on the standard version.
What is a Polyfill?
A polyfill or shim refers to a more or less lengthy piece of code that allows older browsers to support HTML, CSS, or JavaScript features that were not natively available to them.
So don't be surprised if many of your website's visitors use browsers that don't support the latest web features such as HTML5 assets or SVG format, for example.
In order for you to also capture these users, it is recommended to use polyfills. These pieces of code are practical. They allow you to implement new features, such as those mentioned above, on web browsers that originally did not support them.
What are the differences between the standard SDK and slim SDK?
Since the module is developed in ES6 with recent JS functions, we transpile and use the core-js library, which has the effect of filling the gaps of the oldest browsers.
If you already have such polyfills, you can consider integrating the slim SDK.
How do I switch to the slim SDK?
Nothing simpler, just change the name of the SDK you want to call:
instead of
