You really should take benchmarks with a grain of salt, but: https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/go-node.html https://benchmark

You really should take benchmarks with a grain of salt, but: https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/go-node.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... There are others as well like: https://programming-language-benchmarks.vercel.app/go-vs-javascript https://programming-language-benchmarks.vercel.app/go-vs-jav... That being said, the specific performance characteristics isn't really the point. Even if you accept JavaScript and Go being similarly fast (same order of magnitude), JavaScript uses way more memory (which I'd argue doesn't really matter, but it's worth mentioning) and the DOM is the main bottleneck in the browser, so WASM won't save you completely there.