Page Load Speed Issue

Avatar

Avatar
Shape 1
Level 2
sanmeetc6160450
Level 2

Likes

20 likes

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Shape 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Shape 1
Level 2
sanmeetc6160450
Level 2

Likes

20 likes

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Shape 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
sanmeetc6160450
Level 2

18-05-2020

What is the best practice of Adobe Launch implementation to minimize the page load speed?

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 1
gaurav_kd606277
Level 1

Likes

2 likes

Total Posts

7 posts

Correct reply

1 solution
Top badges earned
Validate 1
Give Back
Boost 1
Applaud 5
Affirm 1
View profile

Avatar
Validate 1
Level 1
gaurav_kd606277
Level 1

Likes

2 likes

Total Posts

7 posts

Correct reply

1 solution
Top badges earned
Validate 1
Give Back
Boost 1
Applaud 5
Affirm 1
View profile
gaurav_kd606277
Level 1

29-05-2020

@sanmeet,

 

How are you?

 

Do you have page load times tagged in your website for every page? Page speed usually is a function of synchronous scripts , html rendering on the page, external resources requested(images, fonts, css) and resources afforded to the website by the browser. Asynchronous scripts which are there to measure performance or analytics have a minimal role to play , if any. 

 

Page Top

Loading the launch script itself should not impact page speed and if at all then barely. 

If you are loading it in the asynchronous manner on top of the page and ensuring all third party and adobe analytics tags are executing on the page after page load is complete(this part is critical) , then there shouldn't be any issue. I'll suggest run an audit - how many tags are loading "on top" of the page.

 

Page Bottom

If you still feel about page speed you can have the launch script loaded on bottom of the page. But , then no tags which have the dependency to run on top of the page(like adobe target) can run without some workarounds being added. 

 

 

 

Answers (0)