by eValid » Wed Dec 05, 2012 1:50 pm
The secret ingredient is that "eValid is a browser!" We can put the right hooks in the right place...
What eValid does is put measurement hooks into the processes that handle download of each page component. A "time and volume" wrapper.
After a page component is finished downloading this wrapper reports its data to the eValid parent, which (if you have Detailed Timings turn on) reports the information into the Event Log. A lot of detail, byte count, download time and, perhaps more important, the order in which the download of the component was reported to eValid.
The timing data resolves to 1 msec; the byte counts are just that, byte counts (not an approximate, nearest 1 KB, the exact count).
______________________
eValid Support