NexaGuard
  1. Developer-Reference
NexaGuard
  • Getting-Started
    • NexaGuard Developer Documentation
    • Quickstart (5 to 10 Minutes)
    • Documentation Overview
    • Concepts and Glossary
  • Compliance-and-Standards
    • Compliance Overview
    • IAB TCF v2.3 Support
    • Google Consent Mode v2 Validation
    • TCF API Validation
    • Audit Checklist (Pre-Launch)
  • Web-and-CMS-Integrations
    • NexaGuard CMP SDK – Web & GTM Setup
    • Integrate NexaGuard CMP with Webflow and Wix
    • Integrate NexaGuard CMP with WordPress
    • Integrate NexaGuard CMP with Drupal
    • Integrate NexaGuard CMP with Shopify
  • Mobile-SDKs
    • NexaGuard CMP SDK - iOS Setup
    • iOS SDK API Reference
    • NexaGuard CMP SDK - Android Setup
    • Android SDK API Reference
    • App Attribution Partner (AAP) Integrations
  • Developer-Reference
    • Web JS API Reference
    • Consent Event Schema
    • Deployment and Environments
    • NexaGuard Debug Tool
    • Troubleshooting Playbook
    • Performance and Best Practices
    • Accessibility and UX Guidelines
    • Localization Workflow
    • Migration Guide
  • Security-and-Privacy
    • Security Overview
    • Privacy Architecture
    • Data and Logging Transparency
    • Subprocessors
    • CSP and Network Allowlist
  • Enterprise-and-Legal
    • DPA and Legal Pack
    • RFP Feature Matrix
    • Status and Reliability
    • Support and Escalation
    • NexaGuard CMP SDK – Commercial Licence
  • Operations
    • Changelog and Version Policy
  1. Developer-Reference

Performance and Best Practices

Last updated: February 18, 2026

1. Loader Placement#

place CMP loader as early as required for consent default timing
avoid injecting loader multiple times across templates

2. Script Attributes#

use async/defer only when it does not break consent ordering requirements
test ordering with Tag Assistant and browser timeline

3. Caching#

document cache TTL for CMP assets and config
purge cache after policy-critical updates

4. Anti-Patterns to Avoid#

running multiple CMPs simultaneously
firing analytics tags before consent defaults
conflicting GTM templates writing consent state

5. Mobile SDK Practices#

initialize CMP once
avoid repeated initialization across screens
expose clear consent reopen entry point
Previous
Troubleshooting Playbook
Next
Accessibility and UX Guidelines