UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.40 Safari/537.36

Steps to reproduce the problem:
1. Go to https://www.gamepoint.com/?forceClientTechnology=webgl
2. Register
3. Enter Bingo
4. Check time spend on asynchronously preparing wasm

What is the expected behavior?
Processing time of Chrome for "asynchronously preparing wasm" is over 5 times longer then current public FireFox 56 version

What went wrong?
Chrome WASM is compared to Firefox in very bad shape for months.
Chrome killing Flash is a good choice, but not having proper WASM implementation is not good strategy

Did this work before? No 

Chrome version: 63.0.3239.40  Channel: beta
OS Version: OS X 10.13.2
Flash Version: Shockwave Flash 27.0 r0