Performance and Availability of the Cookie Consent Script
See the OneTrust Cookie Consent Performance Whitepaper for the results of network performance and availability testing.
Performance
Loading the Cookie Banner Script and Preference Center has been designed to minimize page load times by taking advantage of asynchronous loading. The graphic below outlines the process for loading the Banner Script and Preference Center.
-
The
otSDKStub.jsis called by the Cookie Consent Script in the<head>section of the website HTML code. -
The
otSDKStub.jsscript calls theDomain.jsonand theBannerSDK.jsscript asyncronously. The website HTML continues to execute simultaneously. -
The
BannerSDK.jsscript callsgeolocation.jsonp,language.json,Banner HTML\CSS.json, andPrefence Center HTML\CSS.json. -
The
BannerSDK.jsscript uses the information from the JSON files to inject the Banner and Preference Center.
|
Element |
Description |
Size (KB) |
|---|---|---|
|
|
The otSDKStub script initiates the loading of the Banner and Preference Center. |
150
Note:
This size may change as more functionality is added. |
|
|
The Domain JSON provides information about the consent settings. |
0.7* |
|
|
The BannerSDK.js script calls the elements needed to display the Banner and Preference Center. |
79.9 |
|
|
Provides the location of the site visitor to determine which Geolocation Rule applies. |
0.25 |
|
|
Provides the language of the Banner and Preference Center to load. |
4.4* |
|
|
Contains the HTML and CSS elements of the Banner. |
2.9* |
|
|
Contains the HTML and CSS elements of the Preference Center. |
17.3* |
*Configuration Dependent
Availability
OneTrust guarantees a high degree of availability for the Cookie Consent solution through our SLA of 99.95% during a given calendar month. In addition to this, the Cookie Consent solution has segregated the individual components of the Cookie Consent module so that even in the rare case of the main application being unavailable, published Cookie Banners and Preference Centers will not be affected.