Generally, I would use the command promt to perform such tasks using commands such as Ping and Tracert.
I did use, the command prompt to do a ping test, which gives the times it took for 32 bits of data to hit the cutrin server and come back. In this case, one average, out of the 4 times the data travels, it took 216 ms. The highest duration it took to travel was 225 ms and the lowest time taken was 212 ms.
The next part of the task was to perform a trace route to curtin.edu.au.
The name itself is self-explanatory. It basically traces the exact route the data is taking to hit the curtin server. In taking this route, the data 'hops' from one server to another. Obviously, the lower the number of hops, the better the speed is. In this case, even though the command prompt would give the exact same results, a tracing client named Visual Trace Route has been used. The results provided by this client, are hence confirmed by peforming the same test by using the command prompt which gives the exact same result.
There are a total of 12 'hops' between my private IP and the curtin web server's IP address. This is a reasonable number, as anything much higher than this would mean an extremely slow internet connection.
These tasks being completed already, I look forward to completing the remaining tasks in the near future.
Glenn