The hand signs are ASL (American Sign Language) numbers.
![enter image description here](https://cdn.statically.io/img/i.sstatic.net/ERMX3.gif)
The author of the site implemented the page counter by calling two PHP scripts for each page:
http://www.young.com/count/count.php?page=young
http://www.young.com/count/small.php?page=young
Each one of these scripts contains Javascript to insert the correct images for the corresponding number.
However, the implementation is quite buggy. In particular, one of the numbers will always be higher than the other, since (apparently) each script independently increments the page counter. Which one will be higher depends on the order that the browser sends the requests, and the order the server processes them.
Additionally, if two or more people try to access the page at the same time, their requests may interleave, resulting in the apparent count increasing more than once.
For example, for the images you gave we can translate the hand signs into Arabic numerals:
count.php small.php
---------------------
183 130
2 3
29 10
390 389
The Wayback machine seems to be loading the script files in reverse order, and seems to be waiting some time between subsequent accesses.
When I accessed the page, I got 30/27
, 35/36
, and 39/40
.
This has been an example of how not to implement a page counter.
Update
I've been calling one of the scripts in a loop, and the count doesn't seem to wrap around at 1000. It's probably a daily/weekly/monthly count.
The count has decreased back to zero, although it briefly went above 1000.
After some further tests, it looks like the counter is resetting randomly, with more frequent resets under higher server load. Looking at the quality of the code, I'm assuming this is some sort of race condition in the PHP script that wipes out the counter if two or more threads try to modify it at once. (I once had a small website that stored some persistent data in a flat file, and struggled with this problem for some time. The solution is to use a real database.)