Repository navigation
Measure Total Blocking Time per soft navigation - #2586
Merged
Merged
Conversation
On a soft navigation the document stays the same, so the long task buffer still holds the work of every earlier route. Total Blocking Time grew with every step of a user journey: four routes doing the same 200 ms of blocking work reported 451, 651, 851 and 1051 ms. Later pages then failed budgets because of earlier pages' work. FCP and LCP were already measured from the soft navigation start but the long tasks were not, so nearly every task counted. Long tasks are now limited to the measured soft navigation, the same way CLS already is, and use the same start point as the paint metrics. Fixes sitespeedio/sitespeed.io#4892 Assisted-by: Claude Opus 5.5 noreply@anthropic.com
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.
On a soft navigation the document stays the same, so the long task buffer still holds the work of every earlier route. Total Blocking Time grew with every step of a user journey: four routes doing the same 200 ms of blocking work reported 451, 651, 851 and 1051 ms. Later pages then failed budgets because of earlier pages' work. FCP and LCP were already measured from the soft navigation start but the long tasks were not, so nearly every task counted.
Long tasks are now limited to the measured soft navigation, the same way CLS already is, and use the same start point as the paint metrics.
Fixes sitespeedio/sitespeed.io#4892
Assisted-by: Claude Opus 5.5 noreply@anthropic.com