> ## Documentation Index > Fetch the complete documentation index at: https://developer.onetrust.com/llms.txt > Use this file to discover all available pages before exploring further. # Server Side Rendering Performance & Availability # SSR - Performance and Availability of the Cookie Compliance Script ## What is Server Side Rendering? Server-side rendering (SSR) is an application’s ability to convert HTML files on the server into a fully rendered HTML page for the client. The web browser submits a request for information from the server, which instantly responds by sending a fully rendered page to the client. ## Benefits of SSR * A server-side rendered application enables pages to load faster, improving the user experience. * Webpages are correctly indexed because web browsers prioritize web pages with faster load times. * Rendering server-side helps efficiently load webpages for users with slow internet connection or outdated devices. ## How to request SSR Please reach out to your Technical Account Manager, Implementation Consultant, or reach out to to have SSR enabled for your tenant ## How the Cookie Banner and Preference Center Loads 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. ![](https://my.onetrust.com/servlet/rtaImage?eid=ka03q000000kPmb\&feoid=00N1Q00000TQMLt\&refid=0EM3q000001hgBP) ### Description 1. The `otSDKStub.js` is called by the Cookie Compliance Script in the `` section of the website HTML code. 2. The `otSDKStub.js` script calls the `Domain.json` and the `BannerSDK.js` script asyncronously. The website HTML continues to execute simultaneously. 3. The `BannerSDK.js` script calls `geolocation.jsonp`, `language.json`, `Banner HTML\CSS.json`, and `Prefence Center HTML\CSS.json`. 4. The `BannerSDK.js` script uses the information from the JSON files to inject the Banner and Preference Center. ## Download Sizes | Element | Description | Size (KB) | | ------------------------------- | ---------------------------------------------------------------------------------------------- | --------- | | otSDKStub.js | The otSDKStub script initiates the loading of the Banner and Preference Center. | 3.8 | | Domain.json | The Domain JSON provides information about the consent settings. | 0.7\* | | BannerSDK.js | The BannerSDK.js script calls the elements needed to display the Banner and Preference Center. | 79.9 | | Geolocation.jsonp | Provides the location of the site visitor to determine which Geolocation Rule applies. | 0.25 | | Language.json | Provides the language of the Banner and Preference Center to load. | 4.4\* | | Banner HTML\CSS.json | Contains the HTML and CSS elements of the Banner. | 2.9\* | | Preference Center HTML\CSS.json | Contains the HTML and CSS elements of the Preference Center. | 17.3\* | > 📘 > > The \* indicates this size (kb) is subject to change based on your OneTrust Admin configuration. ## Availability OneTrust guarantees a high degree of availability for the Cookie Compliance solution through our SLA of 99.95% during a given calendar month. In addition to this, the Cookie Compliance solution has segregated the individual components of the Cookie Compliance module so that even in the rare case of the main application being unavailable, published Cookie Banners and Preference Centers will not be affected