1. without concurrency
2. if GC end up being provided by the execution environment
3. without the need to support networking and file-system (assuming this has to go through JS)
The go runtime for WASM could potentially be much smaller than the size of the standard server side runtime.
I forgot to note, if lots of page use this runtime and its loaded as a separate cacheable asset with a long TTL, the chances of it being cache are pretty great. Go didn't get popular for FE and I was writing a webapp FE in it I might stick it local storage too...
GopherJS apparently struggles with binary size too [2] (though that's not WebAssembly).
[1] https://blog.golang.org/go1.7-binary-size [2] https://github.com/gopherjs/gopherjs/issues/136