by eValid » Mon Nov 08, 2010 5:22 pm
Episodes uses JScript in the browser and if the implementation is good then the overhead may be quite small.
In eValid, which does NOT run with JavaScript at all, timing details are taken essentially by direct instrumentation of the browser.
We specifically chose this route to keep any error to the lowest possible value. You have to be careful to make sure that the code -- in your case the extra Javascript -- does not perturb or skew the data you are trying to collect. You would need to make sure you are comfortable with the JS overhead introduced measurement error.
About "ease of use" all I can say is that I ran a test on the Episodes demo page and extracted all of the page element timings with a total of 4 clicks using the out of the box settings. The timing data for the JS elements shows up clearly in the event log. The clicks are: (1) Start Recording (2) End Recording (3) Playback (4) Examine Eventlog. Navigating eValid to start on the page of interest is extra. (By the way, the data in that example page is either wrong or maybe the page is out of date?)
_____________________________
eValid Tech Support Team
