Multiple ports after Keep-Alive

I wanted to analyse random website and to see how it behaves when Keep-Alive headers are being sent from my browser(Chrome). The web server responds that it accepts Keep-Alive but what i noticed in Wireshark is that during this time, multiple sockets were opened and closed when loading the website. There were 6 sockets opened during the time from loading the page all the way till closing it. I wanted to make sure it is like this on other websites, but the result was the same. I tried also visiting HTTP/2 website and there was only 1 socket opened all the time which was reasonable. What is the actual reason that Keep-Alive headers are not being respected from my Chrome browser when visiting HTTP/1 websites that accept Keep-Alive header?