Warning: "The AudioContext was not allowed to start."

[theNeedle]

It’s not a problem. If everything else is working, you can safely ignore that.

AudioContext was not allowed to start

It’s “normal” to get one AudioContext was not allowed to start warning, I think, because Phaser tries to create a Web Audio context automatically when the game boots. Can you expand the warnings in the console and look at the stack trace? I think Phaser also tries to unlock (resume) the context automatically when a user clicks. Phaser queues these events, so Chrome doesn’t consider them as coming after a user gesture, I think.