VisitorAPI.js, AppMeasurement.js and Interaction to Next Paint

[PatrickBrownCF]

With Google's upcoming change to make Interaction to Next Paint (INP) the new key metric for Core Web Vitals, I have started working on optimizing my website to get the INP score to under 200ms.

I have noticed that the VisitorAPI file and AppMeasurement scripts have processes that are quite long. Long is a relative term as we are discussion milliseconds, but every ms helps for this.

You can see the timing in the attached image. It is 23.4ms for the scripts to run through tasks and 16.6ms is just for the getAudienceMangerBlob function.

I am wondering if this function needs to run if I am not using Audience Manager and if there is a way to disable it. 

Any insight on this would be helpful.

To note, this is from VisitorAPI v5.4 and AppMeasurement v22.4

[Jennifer_Dungan]

That is interesting.. We don't have Audience Manager either, and we are working on our Core Web Vitals as well... can I ask what tool you are using to get these screenshots so that I can see if we too have that call, and if I can find a solution?

[PatrickBrownCF]

That is just from the Performance tab in Google Chrome:

https://developer.chrome.com/docs/devtools/performance

Just click record, click around the page and check the interactions. It is a bit cumbersome to drill into each script process that is running, but it was very enlightening in terms of seeing processes that were unexpectedly running. 

[Jennifer_Dungan]

Thanks, I will look into that and come back with my thoughts