A page makes one database query per displayed item. What is the problem and how would you fix it?

This is often an N+1 query patte : one query loads the list and another query loads related data for each row. Measure query counts and latency to confirm it. Fetch required relationships through an appropriate join, eager loading, or a bounded batch query, and select only needed fields. Ensure joins do not duplicate parent rows or break pagination. Add indexes supported by the query plan. A single enormous join can also be inefficient, so compare approaches with realistic cardinality and response-size limits.