Repository navigation
Conversation
This branch has not been deployed
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.
#518 slow-phone follow-up: defer Social from initial Me load
The Me screen no longer waits for the 151,959-byte Social script. The current whole-file static budget is 44,810 bytes gzip-9; that is not a measured net saving. After Me's content is useful, the app warms Social during idle time. Social is also loaded before the feed, activity details, friend/profile, group and notification routes that need it.
The small profile-link and friend-count helpers stay eager, and the weekly recap share item loads Social if tapped before warmup. Cook and recipe-import keep their existing first-tap loader and do not pull in Social. A failed Social route load keeps the existing visible “Try again” control.
The exact-main baseline on
111d1e3fwas 4,143 ms to useful Me and 4,268 ms to card actions, with 88/89 requests and no errors across three fictional cold runs. Sage approved the checkpoint. The focused browser test and three comparable after runs are pending an available isolated test slot; no full suite has run.390 px captures (fictional account)