Adobe Launch script load time takes 500 to 900 ms (Network Tab)

[Jayakrish]

Hi All,

We have implemented the site through asynchronous call with adobe launch and recently noticed that the launch script take more time (500 to 900 ms) than usual while we checked from network tab. Please refer the attached screenshot for the reference.
Understand this may vary based on each network and based on individuals network speed. At the very first time on the page it takes 500 to 900 ms and after it get cached and loads it normally between10 to 50 ms.

I feel like I am missing some points to understand this behavior. What are other reason for taking more time to load the launch script at very time?

Thank you,
Jay.

[yuhuisg · Accepted solution]

The 2 main reasons are:

1. Size of the JS file, which depends on all of the assets (rules, data elements and extensions) that you have built and published into a library in your Launch property.
2. Network latency, which is out of your scope because that depends on a whole host of external factors, e.g. ISPs, DNSes, routers, etc.

Obviously, the one to tackle is the JS file's size. I suggest reviewing your Launch property in this order:

1. Disable any Rules, Data Elements and Extensions that are not needed. Disabled assets don't get published to the JS file.
2. Only include the Events, Conditions and Actions that are really needed in each Rule.
3. Remove unnecessary _satellite.logger statements.
4. Refactor your Custom Code to remove and/or simplify them.

[Jayakrish]

Hi Yuhuisg, Thanks for listing our the reason and one of them is already suspected from our side which is network latency. In regards to file size, unfortunately we have just used standard page load tracking (1 rule, 20 Data Element and 3 extension) with up to 35 to 50 KB on each load. Also, we have never used any unnecessary assets and _satellite.logger statements anywhere on the code. Also, be informed that only at very first hit we see between 500 to 900 ms and other next hit it get cached and loads the page normally between10 to 50 ms. Can we then categories this under the network latency issue. I see most of the sites including other external sites are also facing the same network latency. Should we discuss this internally with our network team by any chance? please let me know if I have missed any. Thank you, Jay.

[yuhuisg]

@Jayakrish yup, I suggest you discuss internally. Also, do some timing checks outside of your office, e.g. at home.