My app renders long lists or tables (hundreds or thousands of rows: activity feeds, search results, admin tables, message threads) and the page gets slow or janky when the list grows. Find every place I render an unbounded list and fix it: 1. Identify each list, its current item count in realistic use, and how it grows over time. A feed that shows 50 items on day one shows 5,000 after a few months of real usage. 2. For each one, recommend the right fix: - Pagination or 'load more' if the list is primarily for browsing and SEO or deep-linking matters. - Virtualization (windowing) if the user needs to scroll continuously through large data: render only the visible rows plus a small buffer, recycling DOM nodes as the user scrolls. - Both, if the list also fetches data in pages. 3. Implement the chosen approach. If virtualization: handle variable row heights if my rows have them, keep scroll position stable when items load, and make sure keyboard navigation and screen readers still work (virtualized content shouldn't vanish from assistive tech; use the appropriate aria attributes and count announcements). 4. Make sure the fix doesn't break existing features: selection, inline editing, scroll-to-item, 'jump to latest'. Don't virtualize short, bounded lists (a settings page with 20 items doesn't need it). Don't break find-in-page expectations without telling me the tradeoff. The deliverable is the updated list components plus a note on how to verify: measure scroll smoothness and DOM node count before and after with a large dataset.