Optimize LWC rendering performance for large data sets

• Paginate server-side or client-side limiting visible rows to 50-100 • Virtual scrolling for long lists rendering only viewport DOM nodes • Use track for stable keys in for:each preventing unnecessary DOM rebuild • Defer non-critical secondary data loads after initial paint • Avoid deep @track on large objects—mutate arrays immutably with intention • Profile with Chrome Performance tab identifying expensive getters • Lightning Datatable native features before custom HTML tables