The CardioLog agent is composed of 300 Kb of JavaScript code. 270 Kb of this code is cached in the client browser. The tracking code is loaded on "page load", and connects with the CardioLog server in an asynchronous manner - without affecting the SharePoint page.
What is the impact of the CardioLog JavaScript tracking code on the SharePoint page response time?
Have more questions? Submit a request
Article is closed for comments.
0 Comments