I may have rather serendipitously implemented HTTP/3 support for a Flask-like CMS.

Does HTTP/3 reduce server requests by concatenating multi-resource requests into a single request conveyed through a "chained-path"?

For example:

Loading example.com/about requires loading style.css and favicon.ico.

HTTP/2 would request example.com/about, request style.css, request favicon.ico.

Does HTTP/3: request example.com/about & style.css & favicon.ico with a single request path similar to "/about/style.css/favicon.png"?

Any insight would be appreciated. Thanks!