Thanks, this is useful. The "too long / needs headers" point is fair. I was trying to answer trust questions in the page, but I can see how it turns into a wall of text. I’m going to tighten the first screen and make the sections easier to scan.
On the free-demo-download problem, I’m seeing the same thing so far: "free" does not create action by itself. My current read is that people still need a very fast answer to three things:
1. Is this for my exact situation?
2. What do I get in the first 30 seconds after downloading?
3. Can I trust/inspect it without wasting time?
For asset packs, I would probably make the first screen show one concrete use case, one actual in-engine preview, and one tiny sample of what is inside before the longer description. Then I’d watch referrers/views/downloads separately, because if views are low the page may not be the real problem yet.