Certain page load actions always shows high 'Network time', with the W3C phases showing high 'Redirect time'.
Network consumption: (requestStart - actionStart) + (responseEnd - responseStart)
Example: the page in question, is the home page of a client's financial system.
User would load the home page (https://secure.company.com), provide login credentials and log in. During this process, the user ID is checked and then the user's profile + financial dashboard is loaded - many services are involved in this process, all gathering data for the user's dashboard page, which is loaded after a period of time (https://secure.company.com/landingpage.aspx).
There is no extra info on the redirect time and they're asking if the redirect time includes the total time from login until the user's dashboard page is loaded? If so, would we see the authentication as a separate PurePath and the loading of the user's financial data, as a separate PurePath?
I've attached example screenshots, in case it'll help.
PS: the screenshots were provided by the client; unfortunately, they are not from the same page load, but it does show the items in question and how much time is spent on redirect, out of total time.
Solved! Go to Solution.
Thanks @Clemens F. for confirming redirect forms part of network time.
Can you perhaps help explain why the redirect time is that long in their case though? Am I correct in saying that it considers the time it takes from the 1st URL that is accesses, until the 2nd URL is loaded, as per my example/explanation in my original post?
Is there any way to further analyse redirect time? Client consistently sees high network time, mainly caused by redirect time and they want to understand where the time is spent, exactly. I don't know if this would be possible in Dynatrace?
For those who come across this thread and face a similar situation: the WebEx to investigate this further, never took place. However, we did get to the bottom of the 'issue', after someone at the client, who understands their application better than I will ever do, had a look at it too.
The 1st request i.e. loading of the user's portal page after clicking on the login button, shows the high redirect time. However, there is a 2nd request, which handles gathering of the info to be displayed on the portal. This 2nd request is seen as a separate request and is not tied up with the one showing the high redirect time. When we compared the redirect time with the 2nd request's time, they match.
What is not clear and might require further investigation, is why these two requests are seen as completely separate requests and why the 2nd is seen as 'redirect' time on the 1st. Perhaps there is a need for better configuration in Dynatrace, or is this handled as designed?