Widget Performance Issues
The Arqam360 consent widget is designed to be lightweight, but certain configurations or network conditions can affect performance. Here's how to optimize.
Performance Metrics
- Widget script size: ~8KB gzipped (combined) or ~3KB (split loader)
- Time to interactive: typically under 200ms on broadband
- Largest Contentful Paint impact: minimal (banner renders after LCP)
- Cumulative Layout Shift: near zero (banner is fixed-position)
Optimization Steps
Use split loading
Switch from widget-v2.js to widget-loader.js for 60% faster critical path.
Check hosting
The CDN should be fast globally. If you're self-hosting, ensure proper caching headers.
Minimize categories
Fewer consent categories mean a simpler banner that renders faster.
Disable unused features
Turn off TCF 2.3, GPC, or quarantine if you don't need them.
Verify no conflicts
Other consent tools on the same page can cause conflicts and slow loading.
Split Loading Explained
Split loading separates the consent widget into a tiny loader (widget-loader.js, ~3KB) and the full UI (widget-ui.js). The loader handles critical consent signals (GCM v2 default, cookie check) immediately, then loads the UI asynchronously. This is recommended for MENA markets with slower connections.
Was this article helpful?