/ /

Optimizing Osano Consent Manager (CMP) for Performance

Updated 4 months ago

The settings below focus on improving load times and reducing package sizes for the Osano CMP. Not every option will apply to every configuration, but each can/may have a positive impact performance depending on your setup.


1. Disable IAB Support (if not required)

Difficulty: Low (Osano setting)

  • Go to Osano Admin → Settings.

  • Locate the IAB TCF 2.x framework toggle.

  • Set it to Disabled if your business does not require IAB support.

  • Publish your configuration.

Why: Disabling removes all IAB-related code from the osano.js script, reducing package size. Note: Only disable if IAB is not a business requirement.


2. Enable Split Payload (Premier only)

Difficulty: Low (Osano setting; Premier license required)

  • Go to Osano Admin → Settings.

  • Enable the Split Payload option.

  • Publish your configuration.

Why: High-priority requests load first, while lower-priority requests load asynchronously after the DOM loads. Note: Impact may vary depending on how your website renders data.


3. Optimize Rules

Difficulty: Medium (admin work in Osano portal)

  • Review existing rules in Osano Admin → Rules.

  • Replace multiple regular expressions with broader path matches where possible.

  • Consolidate similar rules into fewer, more efficient patterns.

Why: Fewer complex regex patterns = faster rule processing and less overhead. Check out the Best Practices Guide on rule making.


4. Adjust Script Load Order

Difficulty: Medium (requires engineering/development support)

  • Keep the Osano script in the <head> of your site.

  • Adjust script order so that essential content-rendering scripts load first.

  • Ensure Osano loads after those scripts but still before user-facing content requiring consent control.

Why: Prevents Osano from blocking critical rendering paths while still enforcing consent.


5. Use Inline Classification

Difficulty: High (requires engineering + dev team coordination)

  • In your HTML, replace src attributes on scripts/iframes with data-src.

  • Add data-osano="CATEGORY_NAME" (e.g., MARKETING, ANALYTICS).

  • Example:

<iframe width="560" height="315" data-osano="MARKETING" data-src="https://www.youtube.com/embed/abc123"> </iframe>

  • Publish updated HTML with these inline tags.

Why: Moves classification logic into your HTML, reducing dependency on external classifications and improving performance. Read more on inline classification.

Was this article helpful?
Subscribe to receive updates on this article