If I want to know more I would go to documentation or tutorials.

See, that's not normal, though. You shouldn't need to "dig deeper" to find out what a product is or what it does.

The well-designed homepage should simply tell you that within seconds of visiting. Any additional clicks should only be to "learn more", but not to learn about.

If this was an analogy, imagine a street lined with restaurants.

On one side you've got "Vinny's Italian Pizzeria", "Joe's Burgers and Fries", and "Mary's Bakery and Treats". Each has posters of what they sell posted on the windows, and a QR code to their online menu.

On the other you have "Sal's Food", "Frank's More Food", "Sal's". The windows are either covered in brown paper, or have stock images of "food", but nothing specific about what they actually make. To learn more, you have to go inside, ask someone for a menu, wait for that menu, then have a look. But the menu lacks photos! You either have to know what they are describing to you in the menu, or you would have to have already dined there before.

Does the latter experience sound good? Because that's how too many open-source projects present themselves, and it's to the loss of the volunteer devs and their potential user base.