Reading the benchmark script, and the explanation of it at github, I think the deviation is there to account for floating point artifacts. I.e. where JS = 0.01499.. and GPU = 0.01500.., that's fine, but if the numbers (read results from the fractal function) are deviating more, that's an error.
Edit: Actually, "(JS: 0.56, JS&Turbo.js: 1.74)" seems to be a valid result from what I've seen. May just be that the chosen deviation value is an unfortunate edge case.
It works on my Note 3, but not on my S7. The N3 results are about 1.5/3.0 for me. Though wildly varying between runs.
Edit: It works on my windows PCs (even in a qemu KVM instance using the std vga, but of course the emulated GPU is slower). However, it doesn't seem to like any browser on linux.
From what I can gather from the BOW discussion (see my link below), it's a kind of custom arch distro (https://cdn.turbo.run/alwsl/alwsl.sfs). AFAIK WSL is just a rootfs extracted by the lxrun cmdlet. So I guess this replaces Microsoft's rootfs with arch. It seems to be modified to work around some issues in WSL.
Edit: Actually, "(JS: 0.56, JS&Turbo.js: 1.74)" seems to be a valid result from what I've seen. May just be that the chosen deviation value is an unfortunate edge case.