A standard implementation of AudioEye on a typical web property delivers approximately 100kB of compressed JavaScript to a client’s browser, via our global CDN. The actual size of the code depends on the number of custom JavaScript functions that are required to remediate a given webpage.
Users accessing an AudioEye-enabled website via standard broadband connection or fourth-generation mobile connection should expect to see the delivery times of approximately 200 - 400ms for the software to load. As this load time only takes place after the original page has fired its document-ready event, and is done so asynchronously, via JavaScript, there should be no perceived difference to an end user viewing a site with or without AudioEye.
Does AudioEye impact loading times or site performance?
