How does your DOM measurement tines differ from what I can measure over on the server side?
We are guessing that you mean the DOM timing data described in the SaveRecord command described here: http://e-valid.com/Products/Documentati ... ecord.html
The elapsed time %e, %E, %f and %F values is measured with an internal clock with 1 microsecond resolution, and the times are expressed as the [correctly rounded] nearest 1 millisecond.
If you imagine that the in-browser action is to navigate to a new page on the same website where you are measuring, then you have to include the time it takes from when the browser initiates the navigation to when the server receives the request.
If the web or a network is involved, then you have to realize that the transport times in the web or the network will increase total time.
So, this says that whatever you measure on the server is going to be consistently slower by whatever delays the web or the network introduces.
Also, note that the timings you get this way depend also on the speed of the machine where you are running the eValid browser.
The faster the machine, the faster (smaller) the times Will be.
That'll be independent of the web/network delays.
-- eValid Support