The general idea is that there are many noise sources which technology normally needs to route around. To find random number sources, you reverse this.
Aside of that, you get no direct hardware access to measure and even if you would, there is still the timer resolution problem.
Very recent browsers provide an API to get strong random numbers, but this is even less widely available than web sockets.
So either you take the mouse movement or you use something like Java or Flash, or you use bad numbers.
The JS time function returns epoch milliseconds, not seconds. At the scale of network latency (hundreds if not thousands of milliseconds), the lower order bits should be effectively uniformly distributed. Resolution isn't your problem, the number of usable bits per network call is.
x=new Date().getTime(); for(j=0;j<10000;j++); y=new Date().getTime(); for(j=0;j<10000;j++); z=new Date().getTime(); alert(x+' '+y+' '+z)
gives me high resolution timestamps:1311577733069 1311577733083 1311577733099