Since each stream has its own error control, if one stream experiences an error (e.g., lost or damaged segment), the other streams are unaffected.

With N streams, the overall throughput can be increased by a factor of N, since each stream has its own separate congestion control.

Streams allow concurrent retrieval of web objects, while avoiding Head of the Line (HOL) blocking.

QUIC performs both congestion control and error recovery different from TCP, leveraging all of the knowledge that has built up since TCP was first standardized, and therefore has better performance than TCP.

QUIC’s performance can be better optimized at the application-layer, so it will have better performance than if these functions were implremented in the operating system.

As an application-layer protocol, QUIC can be updated/modified at “app frequency” rather than at the frequency of operating system updates.

QUIC can establish all connection parameters (security, reliability, flow and congestion control)in just one handshake rather than separately in two.