It depends on how you configure it. Any option you choose, make sure the first frame is informative.
What matters is what the defaults are.
That's not what the GP saw.
Firefox seems to only render MP4 files that use yuv colorspace and aa3 audio channels, which require specific ffmpeg flags during transcoding. It took me a day of grinding whackamole to find the magic set of arguments to make all recent, popular browsers actually display a video:
https://github.com/photostructure/photostructure-for-servers...
FWIW, if you really want to encode your video in Rec. 2020, you'd almost certainly want a 10-bit encode, and then you're outside what e.g. iOS devices will render again. Rec. 709 is the safe choice.
Some of this is also probably due to using ffmpeg directly, tbh. It's very happy to produce irrational combinations of things that are technically allowed by specs but not implemented anywhere in practice, often exacerbated by it trying to preserve metadata / colorspace / etc where technically possible.
I do not think even sites like Dribbble have figured it out. I have a lot of issues there with videos.