It depends on your case. If talk in general.
First, it is for the computational performance improvements (You can check the performance comparisons
here). For example, if you are using Compose for Web, using K/Wasm instead of K/JS could multiply the speed of your application drawing.
Bundle size is also a metric that you could care about, and the wasm binary could be much lighter than a JS bundle, so your users could start interacting with your application sooner.
Also, we are trying to make K/Wasm types stricter than K/JS, which means a safer (from bugs) development environment (You can check the overview
here).
This is my point of view, and I think
@bashor could also add several points.