review-performance

# Review performance Run a **performance-focused** review: algorithmic complexity, data structures, memory leaks, bundle size, critical path, cache strategy, images, and Worker cold starts. Your reply must be a **plan of suggested changes**: concise, actionable, and structured-not only prose. ## Invocation Text after the slash command is additional scope/focus - narrow the review accordingly. If none given, use the default scope described below. ## Best practices alignment - **Algorithms and data structures** - Prefer O(n) or better for hot paths; avoid redundant loops, repeated sorts, or nested iterations over large collections; use appropriate structures (Map/Set for lookups, avoid repeated array scans). - **Memory** - No closure or WeakRef leaks in long-lived Workers; no unbounded caches or growing global state; React effects and subscriptions cleaned up on unmount. - **Frontend** - Critical path minimal; lazy load below-the-fold; `fetchpriority` for LCP; explicit dimensions to avoid CLS; code-splitting and tree-shaking; prefetch where beneficial. - **Caching** - Cache TTLs and keys match content type (HTML vs assets vs API); no over-caching of dynamic content or under-caching of static; Cloudflare asset and API cache headers correct. - **Worker and API** - Bundle size within limits (e.g. < 1 MB compressed for Workers); no blocking I/O on critical path; cold start impact minimized (small deps, no heavy init). Align with root [AGENTS.md](../../../AGENTS.md) and ap...