I have run benchmarks directly with the actual codebase running on my computer and then the WASM version and the WASM is about 70-80% of the speed. Sadly, when

I have run benchmarks directly with the actual codebase running on my computer and then the WASM version and the WASM is about 70-80% of the speed. Sadly, when the analyzer was written in Go, I was getting around 20-25% of the speed after compiling to WASM. I believe it is largely due to that code being very inefficient about allocations, and I think WASM doesn't like allocations/deallocations very much.