Database performance work should begin with evidence. A slow dashboard may be caused by missing indexes, repeated queries, excessive result sets or unnecessary joins. Measure the actual endpoint and inspect the generated SQL before changing the schema. Use EXPLAIN to understand access paths and row estimates. Index columns used for frequent filtering and joins, and think about the order of columns in composite indexes. For example, tenant-specific records often benefit from an index starting with company_id and followed by the most selective or frequently sorted field. Indexes are not free. Every additional index consumes storage and adds work to inserts and updates. Avoid indexing every column in isolation. Paginate large collections and select only the fields needed by the current screen. Finally, compare results after the change. Capture query time, explain plans and realistic dataset sizes. The objective is not the highest number of indexes; it is predictable performance under real user workloads.