Improve events page loading - #273
Open
olivia2450 wants to merge 5 commits into
Open
Conversation
|
🚀 Preview deployment is live: Preview Link |
…prove-eventsloading
8 tasks
…prove-eventsloading
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #<issue_number>
🌟 Context
Found that getEvents() and getEventsGlobal() were being awaited sequentially, roughly doubling load time unnecessarily since they're independent fetches. Switched to Promise.all([...]) in EventsPageContent.tsx. This cut steady-state load time to about 3s in local testing.
📝 Description
Added Next.js loading.tsx and Suspense streaming to the events page so the page shell renders immediately on navigation while event data is being fetched, instead of the browser sitting on a blank/white screen until everything resolves.
📋 Notes