Hi! First I would like to clarify My physical Stopwatch says "33,19 ms" -> ~33 sec and if you meant 33,190 ms Secondly, EIP uses data provided by the Profiler which does have some overhead. For example if you were to use Deep Profiling, those times would be even higher. There's also overhead from the windows themselves. As recommended in the original post, best results are achieved by closing most of the windows then checking out the data. You can also try exporting in HTML which will show you the % distribution of those timings (more useful to know the % of time it takes relative to everything else rather than the exact timing). If you want more accurate timings I would suggest you wrap your code with the StopWatch class and handle those yourself. Thirdly, as the Domain Reload takes multiple frames and steps it would be a bit difficult to reflect the real timing of it. What this tool provides is a way to identify frames that would be responsible for the majority of the time.