Relation between Conformance + Landing Page

For me it is not clear how the relation between the landing page / and the conformance page /conformance is. It seems like a client should connect to / and then request /conformance.

1. As the response of conformance is pretty simple, I'm wondering why it is not part of /.
2. At the moment it seems already that /conformance may have implications how I should read /. Would a "xml" conformance mean that the landing page is xml?
3. If I want to extend the landing page with whatever extension (there's already use cases in STAC and openEO), I would need to add that extension to /conformance just to figure out that I may need to revisit /, because it contains more than initially thought.

To avoid this, I really think /conformance should be merged into / so that on the initial request to the landing page I already know what the service conforms to. I guess a client is not expected to visit /conformance before /, right?