# Landing Performance

> Fix performance issues in apps/landing for leaderboards, battles, rankings, vote/reaction summaries, and high-cardinality result pages.

- Skill: `conectlens/landing-performance` (Agent Skill)
- Install (CLI): `npx skillmds@latest add conectlens/landing-performance`
- Raw SKILL.md: https://api.skillmd.com/api/skills/conectlens/landing-performance/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: conectlens (https://skillmd.com/u/conectlens)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/conectlens/landing-performance

---


# Landing Performance

## Rules

- Leaderboards must page or window results.
- Ranking queries must avoid full-table client sorting.
- Battle lists should render summary cards only on first load.
- Expensive aggregates must be checked for index support and payload size.
- Do not request full battle history when only top slices are visible.

## Gotchas

- Rank pages often fail because the UI requests more rows “just in case”.
- Score, XP, reactions, and joins can multiply row cost quickly.