Since moving to Consent Pro, the website performance has gone down massively when measuring on Google PageSpeed Insights, especially bad for mobile.
Consent script is added via the Consent Pro app.
Has anybody else experienced this sort of behaviour and/or found a fix?
Yes, spotted this today on 2 different sites. Would be good to get some support on this asap.
Hello @hello58 @Matt_Connelly! Apologies for the inconvenience. We are taking a look!
Could you share your project’s domain? You can share them by DM if you wish!
Same Issue here for https://bor-ng-immobilienverwaltung.webflow.io/
As far as I can see from a short search, this script added in the webflow section “Code added by apps:” causes this.
const fs_consent_pro_config = {"instances":{"v1":{"domain":"","endpoint":"","expires":"365","mode": ...
The script blocks first rendering and loading of the script should be defered.
I have the same issue for https://ifast-pl.webflow.io/ (test domain).
Is there any workarounds on this?
I published my site one day after Consent Pro came out because I was waiting for it to be ready. Since then, the site is very slow on mobile, even though I made all the images as small as possible.
It looks like the Consent Pro script is causing the slowdown, but I can’t figure out how to load it otherwise and make the site faster. Webflow adds the script automatically, and I don’t have control over it.
Hey, @Support-Luis do you have any updates on our issue?
Hello @here!
We have recently pushed an update aimed at fixing this by implementing an async tag on the main Consent Pro script.
This update is automatically applied if you have generated or edited your component after September 29th.
If you have not modified your Component since then, you can simply follow these steps for the update to apply:
async tag on your main Consent Pro script as shown belowIt is important to note that
All cookie consent solutions affect performance in some way. The difference is that Consent Pro is built to minimize this impact. It loads its script asynchronously (non-blocking), which means your pages render faster and Core Web Vitals (like FCP and LCP) improve.
