Go isn't a very good fit for this kind of thing. I've done it with Rust (Leptos, Dioxus, etc). The wasm binaries are a lot more sane when using Rust. On average, my wasm binary was around 240kb and it compresses really well over the wire.
I should have been a bit more clear. I love memory safety. But I dislike a lot of other aspects specific to Rust. I would much prefer e.g. C with memory safety (somehow). So that is, for me, why not Rust. Rust is more more than just memory safety.
Perhaps you should look into Vale or Pony then, they have memory safety like Rust, also without a GC, but they use different mechanisms for it.
I built https://hackernewsalerts.com for that
Something beam-hosted with zero pointer sharing between nodes and smaller runtime maps to wasm much better.
One WASM-related case I've actually encountered in the wild is Unity web. Similar problem as Golang, the runtime is heavy.
Probably a bit of work but there should be no reason why Go would not be able to do the same at this point.
People tend to think all GC are the same, they are not.
This massively bloats binaries and means that go compiled to wasm is much slower than native speed, significantly more so than than the equivalent slowdown for c/rust.