01 Sep 2021 04:42 AM - last edited on 07 Sep 2021 12:52 AM by MaciejNeumann
Last few days I’ve been looking at the “Page Load Cycle” diagram and explanations provided at https://www.dynatrace.com/support/help/how-to-use-dynatrace/real-user-monitoring/basic-concepts/user..., and the more I look the less sense it makes to me. I also read some related materials at w3.org and other resources but still struggle to find reliable answers on my questions. I would appreciate if someone could help me with them.
a. How such request would be treated in Dynatrace RUM?
All these static elements were delayed by the network (for at least for network Round Trip Time at HTTP 304 Not Modified), but Dynatrace considers this delay as a front-end time rather than network time. Why?
3. App cache.
Usually all the static objects that require to render the page loads after the client executed its main business logic request, or closer to the end of main request processing. That is what I could see inspecting the network traces, looking at Dynatrace RUM waterfall diagrams, but it is even present at the “Page Load Cycle” diagram (css, image, etc.). Why “App cache” is pained right after “Redirect” at “Page Load Cycle”? Is it another kind of cache, not static content but something else?
@daniil_kochetov hopefully Dynatrace Support Reps can provide some clarity on the questions you have provided.
Even thought It's been a while since this thread is posted, I think it raises a couple of really important questions that would be helpful for the future visitors of this forum. Does anyone of you has some tips or thoughts? Would be fantastic, thanks in advance for any feedback!