What is DTM Server response time / DTM library size / DTM Load time /Tips for optimizing load performance?

Accepted Solutions (1)

Accepted Solutions (1)



Dynamic tag management has never shown signs of negatively affecting page load time or execution speed. However, because dynamic tag management can be used as a delivery system (a way to deliver JavaScript, HTML, images, or other Web content), if you load a large file, or a large image at the wrong point during render time, you can slow down page load speed and increase code execution time on that page. If you lazy load images, and if you use asynchronous (non-sequential) scripts as much as possible, and you follow best practices regarding the code you add into dynamic tag management, you should not see negative performance impacts.

The Embed code should be hard-coded in the <head> section of your templates. This is a synchronous JavaScript include. The dynamic tag management engine is designed to work in a modular way, so scripts that do not apply to a particular page, site section, or domain will not load or execute when they are not needed. Most users increase the use of asynchronous (non-sequential) methods when deploying third-party scripts. This generally improves the perceived page load speed for site visitors. While the dynamic tag management main library file itself is loaded synchronously, most clients load any code from within dynamic tag management using the built-in asynchronous methods.

Please see below link for more info -


Answers (2)

Answers (2)


Community Manager


Placing the DTM embed code outside of the header is unsupported. Doing so will lead to unexpected results and issues with various solutions deployed via DTM.

As for Google's PageSpeed insight, I can't speak to how to tool calculates these points, but you can measure real world performance of the page in the browser's dev tools and you will likely see minimal if any impact from deploying DTM.




the problem I have with the synchronous include in <head> is that I get a pretty huge penalty in pagespeed.

You write "should" be hard-coded in head - What happens if I put it near the end of the page instead?

Do you have any experience already with this problem and maybe even some workaround or fix?

In my example I got a penalty of 37 points after implementing Adobe Analytics with PageSpeed Insights from Google (Mobile)