Latency refers to the time delay between a data request made from an end-user's device to reach a server and for the server to respond back to the end-user's device. Minimizing latency as much as possible is important to improve your end-user experience and web property performance.
In this article, we will cover the ways Sourcepoint minimizes its impact on latency for your web property and ways in which your organization can optimize your implementation to improve latency.
CDN caching
Content Delivery Networks (CDNs) improve latency by caching content closer to end-users which reduces the distance the data needs to travel. Instead of traveling to and from the origin servers for every request, cached resources can be served quickly from edge servers in the network that are closer to the end-user.
For end-users who have previously consented on your property, all the necessary data to fulfill requests and respond to relevant functions are stored locally which eliminates the needs for network calls. For new users whose data is not already cached client-side, all network calls needed to display a message and return consent data to the page are served from the CDN.
While cache durations vary, on average endpoints are updated every 30 minutes to pick-up the latest configuration.
localStorage
Utilizing localStorage allows Sourcepoint to store data locally within the end-user's browser. Since this data is stored on the client-side, instead of continually retrieving this data from a remote server Sourcepoint can reduce the number of server requests and retrieve this data faster.
Local storage items
Click here for a list of local storage items that Sourcepoint may store on an end-user device.
Optimize your implementation
Your organization's web property performance and the speed by which your Sourcepoint message loads can be dependent on the methods and styling used to configure your message and how Sourcepoint's tags are implemented. Review the compiled resources below for different strategies you can employ to optimize your implementation and improve latency:
Comments
0 comments