Session timings incorrect due to Client Connected time being used as start point

[Tony]

Hi there, I've used Fiddler occasionally for years, but am new to Fiddler Anywhere. I want to use Fiddler to accurately time page load times of my Dynamics 365 CRM system. I used to do this by filtering on the URL of my CRM system, clearing the traffic window, loading a page, clicking Ctrl+A in the traffic window to highlight all the sessions, and then reading off the total time from start to end (currently shown as the Max Duration figure in the Overview Window).

This method is working for me some of the time currently, but only for about one in three page loads that I test. The problem seems to be related to the "Client Connected" time which sometimes doesn't reset for each page load. In the screenshot below, you can see that I clicked the link in my browser at 11:54:12, but the system is providing a timing which starts at 11:53:59 as the Client Connected time. It incorrectly tells me the session lasted 13.67s when it actually only began at the Client Begin Request time and took less than a second to complete.

Is there a way to tell Fiddler Anywhere to ignore the Client Connected time and measure from Client Begin Request instead? Alternatively, can I force my browser to start a new connection each time I load a page (which it seems to sometimes, if I've been idle for a minute or so)?

Any help greatly appreciated,

Best wishes,

Tony

[Nick Iliev]

Hello Tony,

The "Connect" timing (corresponds to the Client Connected) shows the time needed from the browsers (or the client application) to negotiate the connection with Fiddler.

You can use the filter button in the top-right corner to remove the "Connect" timing from the overall timings. For example, the screenshots below demonstrate the differences in the overall timing with and without the "Connect" timing.

With "Connect":

Without "Connect":

 

Regards,
Nick Iliev
Progress Telerik