You load a browser game, and instead of the game you get a big button that says click to play. Hit it, and the music still might not start. Plug in a controller and nothing happens until you mash a face button. It feels like the game is fumbling the kick-off. It isn't. Most of those pauses come from rules the browser sets, and each one exists so a web page can't do something to you that you didn't ask for.
The quick version: a web page is allowed to show you things, but it has to earn the right to make noise or see your controller, and a click, a tap or a button press is usually what earns it. Once you know which rule sits behind which pause, the rituals stop looking like bugs and start looking like a fair deal.
Sound waits for you to do something first
This is the one that trips people up most. Browsers hold back media that tries to play on its own. In April 2019 Mozilla wrote on its blog that on sites that autoplay video or audio, Firefox would "stop the autoplay before it can start". To hear it, you click play, or you add a site you trust to your permissions list so it plays from the get-go.
The reason is obvious the moment you picture the web without it: every tab you open blaring at you before you've read a word. The cost lands on games, which want their music and effects from the first frame.
Look at how itch.io, the indie storefront, handles it. Its HTML5 documentation for creators says games need a click to start by default, which keeps the game from slowing your browser down while the page loads, and it warns developers who switch auto-start on that "audio may be muted on some browsers". So the click-to-play screen isn't wasted time. It's the game waiting for you before it does anything noisy or heavy.
If a game still comes up silent after you've clicked in, check the obvious things first: the tab isn't muted, and the site isn't on the blocked side of your browser's autoplay settings.
Where it gets messy
None of this is identical everywhere. Browsers handle autoplay differently and settings vary, which is why itch.io's warning says audio may be muted on "some" browsers rather than all of them. A game that's built around the rules can wake up its sound and its controls in one start screen. One that tries to skip the click is the one most likely to come up silent, and that's on the game, not your speakers.
So treat the first click as part of the game. Click into the window before you judge the sound. Press a button before you assume the controller is broken. Use the game's own fullscreen button. The browser isn't getting in your way: it's making the page ask first, and that's a trade worth taking.
Reporting notes



