--- title: "Loading a Consent Banner Without Hurting Page Speed" canonical_url: https://ot.webclat.com/qa/consent-banner-hurting-page-performance description: "Split the render-blocking concern from the payload-size concern - a tiny synchronous consent-default script plus an async-loaded full CMP library, rather than one blocking bundle." source: Webclat | OneTrust Solutions (OneTrust partner, independent consultancy) --- # How do I load a CMP/consent banner without it becoming the slowest script on the page? **Short answer:** Most consent-banner performance problems come from loading the full CMP script synchronously in a way that blocks rendering, or from a single request that bundles a large vendor/cookie database together with the visible banner UI - split the two: a tiny, synchronous script that sets Consent Mode defaults and gates other tags, loaded first, with the heavier CMP library itself deferred to load asynchronously after that. ## Why this happens There are two distinct performance costs, and they need different fixes. The first is render-blocking: a plain ` ``` 3. **Check whether your CMP vendor offers a lighter-weight mode** - Some vendors' fully-hosted script is large because it bundles every possible integration's vendor-cookie declarations by default - check for a self-hosted, scoped-down, or "lite" configuration option that ships only what your actual vendor list needs. 4. **Defer the visible banner's render until after first paint** - Many CMP libraries support a configuration flag to delay rendering the visible banner UI until the page's main content has painted, rather than blocking first paint on banner readiness - use it if available. 5. **Measure with a real performance audit before and after, not just page-load feel** - Run Lighthouse or PageSpeed Insights specifically looking at the "render-blocking resources" and "reduce unused JavaScript" flags, since CMP scripts commonly show up under exactly those two categories when misconfigured. ## How to verify it worked - Run Lighthouse before and after the change and confirm the CMP script no longer appears in the render-blocking-resources list. - Compare Largest Contentful Paint timing with the banner present against a build with it temporarily stripped out, to confirm it isn't regressing LCP once loaded asynchronously. - Confirm the tiny synchronous default-consent script still runs before any gated tag, even with the full CMP library now loading asynchronously - check DevTools Network waterfall ordering to be sure the sequencing wasn't broken by the change. ## Related - [What's the correct pattern to block GA/GTM/AdSense from loading until the visitor accepts cookies?](https://ot.webclat.com/qa/gate-ga-gtm-adsense-behind-cookie-consent) - [How do I make a visitor's cookie-consent choice persist across subdomains instead of re-prompting?](https://ot.webclat.com/qa/cookie-consent-persist-across-subdomains) - [Why doesn't Google Consent Mode v2's ad_personalization/analytics_storage signal update the way I expect?](https://ot.webclat.com/qa/consent-mode-v2-signal-not-updating) Contact: ot@webclat.com | (813) 694-4451 | https://ot.webclat.com/#contact