<instructions>
The bottleneck below is already confirmed. Propose targeted optimizations for it:
- For each change: the change itself, expected gain (order of magnitude is fine), why it is safe (behavior unchanged), and its readability cost.
- Order by gain-to-risk ratio. Stop when further changes buy little — say so explicitly.
- If the real fix is architectural (caching layer, different data model, moving work offline), state it as a separate recommendation with its trade-offs instead of forcing it into this pass.

End with the "verify" step: which measurement, run before and after, proves the gain?
</instructions>

<confirmed_bottleneck>
{{bottleneck}}
</confirmed_bottleneck>

<code>
{{code}}
</code>