Certain actions and pages seem to take longer to load than they could. For me the "add or update card" modal was noticeably slow to load. While poking around in the devtools network tab:
- Opening the modal makes a request for current card (data and media) and a list of the user's collections.
- Opening a second modal does the same thing.
- No data is displayed until both request are complete.
In this case, the data for the card is already available for it to be clicked on. While the list of collections could potentially change in between those actions, a stale-while-revalidate cache or something similar (trying to avoid being prescriptive in an issue) could help skip past subsequent loads. Other places where loading felt slow: reopening the same collection after navigating away, flipping between tabs in profile, sections in settings, editing cards and collections.
These are great points, a lot of these have been on my end-of-year list. I agree that URL metadata and collections fetching should not block user from saving to library. We do have stale-while-revalidate cache, but the stale time is set to be low (reopening the "add or update card" modal for the same card should load the cached data immediately). Same with profile tabs. I think we can adjust these. Settings page too. We're also going to move to Next.js 16 and utilize cache components.