HTTP/1.1 uses a textual message format

HTTP/1.1 defines requests and responses as start lines, fields, and optional message content. A single TCP connection can be reused, but multiple in-flight exchanges have practical ordering constraints; browsers often open several connections to improve concurrency.

More connections consume server and network resources, so connection strategy is a trade-off.