200 orders on a page but 201 queries in the log. Name the problem and give fixes (including JOIN FETCH).

Tests whether you identify the N+1 problem precisely -- one query loads 200 orders, then a lazy association fires a separate query per order -- and fix it with JOIN FETCH, @EntityGraph, or batch fetching rather than just switching to EAGER everywhere, which creates its own over-fetching issue.