Browsers commonly restrict playback with sound until the visitor interacts with the page. A player waiting for a Play click may be following normal policy rather than failing to load the stream. Test a direct user action first.
Separate waiting from buffering
If clicking Play starts the programme immediately, the initial state may be intentional. A loading spinner after the click suggests another issue. Do not count the time before interaction as a network startup failure.
Check the site's controls
A useful web player exposes a clear Play button, mute control and understandable error message. If controls are hidden, report the interface issue to the operator rather than changing browser permissions globally.
Avoid unnecessary permission changes
You may choose a documented per-site autoplay preference in a browser that supports it. Keep the change limited to a trusted site. It will not repair an unavailable media resource or missing codec support.