Repository navigation
perf(pages): cache /projects and /testimonials - #73
Merged
Merged
Conversation
Admin creates, edits and deletes of projects, testimonials and impact stories now call revalidatePath for /projects or /testimonials, so a cached page picks up the change on the next visit.
Both pages ran a database query on every visit and took about four seconds on a cold start. They are now prerendered and rebuilt at most every five minutes, so visitors get a cached page.
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
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.
/projects and /testimonials were force-dynamic: a database query on every visit, about 4s on a cold start and about 1s warm.
The production build lists both routes as static with a 300s revalidate.