Safari on IOS still has a ton lingering HTTP/3 / QUIC bugs. I think it is to the point that if your user base doesn't warrant it, (i.e. you are targeting well

Safari on IOS still has a ton lingering HTTP/3 / QUIC bugs. I think it is to the point that if your user base doesn't warrant it, (i.e. you are targeting well connected devices with minimal latency/packetloss) it's not even worth turning HTTP/3 on