Repository navigation
perf(home): serialize only visible demos - #567
Merged
Merged
Conversation
Collaborator
Author
|
🤖 Harlan Agent Kit verification of head Using the live 42-demo response, the projection produces 17,046 JSON bytes from 72,458 bytes. The local Nuxt payload measured 51,049 bytes. This is not a production reduction measurement: other local feeds differ. |
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.
🔗 Linked issue
❓ Type of change
📚 Description
The homepage serialized every demo, although its two sections display at most nine. Select six teaser demos and three comparison previews before Nuxt serialization, while preserving the full count.
For the 42-demo response, projected JSON falls from 72,458 to 17,046 bytes. The comparison keeps its preferred group and fallback order.