|
Tips for Accurate Web Response Time Measurements
|
Top Previous Next |
| · | Add a CLEAR statement to your macro. This way you can make sure that the browser cache is cleared before each run. Otherwise, iMacros might read the web pages from the cache and not the web server, which would most likely result in lower response times. Whether the cache is actually used, depends on the Internet Explorer settings.
|
| · | Run the measurements as a loop and average several runs. The "internet speed" can fluctuate from minute to minute even on a fast connection. Therefore differences between each measurement run are normal. To get stable results, it is good practice to average several runs. Several common programs such as Microsoft Excel can create averages automatically for you.
|
| · | If you compare results between different PC's, please keep in mind that the accuracy depends on the accuracy of the PC clock. This applies to all software that does time measurements on a PC.
|
| · | Under normal conditions the processor speed does not influence the measured response times. Only if the PC is so slow that the web page rendering of the browser is slowed down, will the CPU speed have an influence on the measured response time. iMacros response time measurements always reflect the true user experience as they are measured using a real browser and the original browser plug-ins such as Macromedia Flash Player or SUN Java runtime.
|
| · | Sample measurements with a modified Demo-Stopwatch macro running on the iOpus.com Dallas monitoring server:
|