A short list of improvements that respect the constraints of a small, static, no-account daily puzzle.
Any small daily puzzle accumulates a list of things the players want that the design has deliberately not done. The interesting exercise is to sort that list by whether the addition respects the constraints that make the game good, because a feature that breaks the constraints is usually not worth having.
The first category is free additions. Better archival browsing, a share card that works without a script, clearer wording around par, and a practice mode that remembers your last difficulty setting in local storage. All of those make the existing design better without adding a server, an account or a data store. They are the kind of improvements a solo builder should do first.
The second category is local-first additions. A personal stats page computed from local storage, an offline-cached daily, a keyboard-only mode. These need care but not infrastructure, and they preserve the property that the game works before anything is set up.
The third category is the one to resist: anything where the value comes from other players. Leaderboards, streaks with public comparison, challenge links that require a server to validate. Each is genuinely better with a backend, and each makes the first play slower and the operator's job larger. A small game should not pay those costs until the demand is loud and specific.
The most underrated item is the one that costs nothing: naming the word lists and the par source plainly in the interface. Most confusion about small puzzles comes from undocumented contracts, and documentation is cheaper than any feature on the list.
The order of the categories is the whole point: local-first additions make the game better for the player in front of you, while social additions make it better for a player who is not there yet.
If you build any of these, test it against the ten-minute player. Then open the practice room and check the improvement on a fresh random start, which is where design problems show up fastest.