Experimental Study
on Web Asynchronicity


Experiments using the "web time noise" as a way of composition.
The noise seen has not been coded with a random function of some sort, it is the network response time and the browser's imprecisions that create the asynchronicity.

The same image is loaded several times in each part of the 16x16 grid, so 256x the same image.
Browsers are smart enough to recognize that it is the same image and will load it only once, and display it everywhere it's needed (that's the [1/1]). In case of animated gifs, they will also keep synchronized.
If it's not recognized as the same image, the browser will then load each image separately and of course, not at the same time.
This experiment fools the browser and make it load the same image several times. Loading 2 images (that's the [2/1]) or 16 images ([16/1]) instead of 1 will take more time, depending on the network and your machine/browser speeds. Loading 256 images (that's the [256/1] will take much more time, resulting in different noises.
Also, after all images have loaded, the browser will have to deal with a lot of precision (animating lots of very fast animated gifs) and sometimes fails at it. This is another layer of "web noise".

[*2] will use a 2 frames animated gif. [*3] 3 frames, [*4] 4 frames.

, and set the image used.