This is assuming best case e.g. no issues in the tcp connection with HTTP/2 > With HTTP/2, any interruption (packet loss) in the TCP connection blocks all stre

This is assuming best case e.g. no issues in the tcp connection with HTTP/2 > With HTTP/2, any interruption (packet loss) in the TCP connection blocks all streams (Head of line blocking). Because HTTP/3 is UDP-based, if a packet gets dropped that only interrupts that one stream, not all of them. So while HTTP/3 on a perfect network might be a 1 - 4% slower it's more stable/reliable in that any packet loss won't cause a dramatic drop off in performance... so 1-4% in best case network conditions but in real world network conditions http/3 should~ be much better...