Product teams tend to make the answer page a finale. Confetti, a big reveal, a share card. After a year of running a companion site for a daily puzzle, I think the answer page should be the least exciting page in the product, and the reason is a design principle that generalises far beyond games.
The player arrives at the answer page after the interesting act has already happened. The two minutes before that page are where the game lives: the listening, the narrowing, the guess. A dramatic reveal page is competing with that experience rather than consolidating it. Worse, it adds latency to the one thing the user came for, which is the answer itself.
What the page actually needs is three things. The answer, above the fold, without a scroll. The hints next to it, collapsed, so someone still working can use the page without being spoiled. And a way back into the game, because a finite experience usually ends with a desire for one more round. That is it. Everything else is decoration that slows the page and makes the answer harder to confirm.
There is an SEO argument too. Answer pages are the pages that rank for question-like queries, and question queries want immediate answers. A page where the answer is buried under a hero animation and three paragraphs of preamble has a worse answer density, and answer density is what users and search engines are both estimating. Plain HTML that states the answer in the first screenful is not lazy; it is the correct product decision for this page type.
I would go further: the boring answer page is a brand decision. A site that respects the player's time after the round is a site the player trusts before the next round. Trust compounds in a way that confetti does not. You can compare the two approaches in five minutes: see the daily answer as it is laid out here, then look at the practice page and notice how much of the design is just removing steps.