Currently, the photographers page loads all of the information about the photographers in a single request which puts a lot of unnecessary load on the backend and causes slowdown for the frontend users.
To improve this, we want to either split the names of the photographers into different tabs based on the alphabetical order of their name (or any other feature, still need to scope this out) and lazy-load them only when a certain tab is viewed or create some sort of filtering/searching boxes to limit the number of photographers that have to be fetched.
The end goal is to have a photographers page that only gives the user information about the photographers that they need and does not put a lot of load on the backend.
Currently, the photographers page loads all of the information about the photographers in a single request which puts a lot of unnecessary load on the backend and causes slowdown for the frontend users.
To improve this, we want to either split the names of the photographers into different tabs based on the alphabetical order of their name (or any other feature, still need to scope this out) and lazy-load them only when a certain tab is viewed or create some sort of filtering/searching boxes to limit the number of photographers that have to be fetched.
The end goal is to have a photographers page that only gives the user information about the photographers that they need and does not put a lot of load on the backend.