I'm far from knowledgeable in HTML and Javascript, however, you can monitor the ongoing network requests (fetching the .wasm would likely duplicate the calls). A quick search hinted at Performance API. You can also edit the composeApp.js, where the fetching of the .wasm field happens, and listen to these. I distribute the files through GitHub Actions, so I could simply edit the generated ComposeApp.js in there before it's distributed and inject any listener to the fetchers.