One GraphQL request must return the whole page - artist, genres, tracklist and reviews together. That is the point of GraphQL versus the REST N+1 pattern. - [ ] route `/album/:id` (code-split as its own chunk) - [ ] `ALBUM_DETAIL` query with nested relations - [ ] DataLoaders make the nested fields a constant number of SQL queries **Acceptance:** opening an album shows the tracklist and reviews with no more than a handful of DB queries regardless of list length.