[T B <phreakocious@xxxxxxxxx>]

This is going to be tricky, especially with HTTP 1.1 connections, as the browser could hold the connection open after the last element has been loaded.  It would be better to look for the last client ACK of a packet containing data, but I don't know of an easy way to get that level of specificity in a filter.  

On Fri, Aug 14, 2015 at 2:59 AM, asad <a.alii85@xxxxxxxxx> wrote:

Hello,

I'm using wireshark to calculate the page load up time for a website. I'm comparing the results from other online tools such as "http://www.webpagetest.org" and see the results don't tally.

My capture filters is:

"dst host 1.1.1.1 or src host 1.1.1.1"

Further, my capture filter is

"!(tcp.flags.reset == 1) && !(tcp.flags.fin == 1)"

I'm looking at page load up time through the following UI "statistics -> summary" and time between first and last packet.

Differences in coming in seconds not ms between online test and wireshark test done from my computer. I'm using wireless NIC card.

Is there a way to tweak the param's on wireshark to bring more close to real results.

regards

asad

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe