Video embeds fail on mobile devices. The useful response is a targeted correction with an observable acceptance check. That keeps the repair tied to the problem instead of turning it into an open-ended redesign.
Find the likely cause
Implementation was checked only in one desktop browser.
Treat this as an explanation to verify against the actual work. Look at the input, the relevant decision, and the final result together. If the evidence does not support this diagnosis, investigate the mismatch before applying a convenient but unrelated fix.
Make the targeted correction
Test responsive sizing and playback on representative devices.
A video page should help visitors understand, watch, and use the video through clear context and accessible supporting material.
Check that the repair worked
Confirm that controls remain visible and usable.
Repeat the check on the final version that the reader or customer will encounter. An approved draft, a preview, and a published result can differ; the acceptance decision should concern the version people actually use.
Prevent the next related failure
A separate issue to watch for is this: several videos share a generic page title. Give each page a title and introduction tied to its content.
Monitor the useful outcome
Track successful playback, relevant viewing behavior, and completion of the task the video teaches.
Keep a short record of the original symptom, the evidence behind the diagnosis, and the result of the acceptance check. That record makes the solution reusable when the same condition appears again, without assuming that every superficially similar problem has the same cause.
Official reference for the platform or standard discussed: Google Search Central: video.