Tighten the Render blocking section: labels, order, precision#170
Merged
Conversation
The blocking counters used to read like single-word measurements
("Render blocking" / "Potentially blocking"), making it ambiguous
whether the number was milliseconds, bytes, or something else.
Spell out that they're request counts. Move the style recalc rows
above them so the actual work (elements touched / time spent)
reads first and the per-class request totals follow as context.
Tighten the recalc labels so the longest one fits the metric
column on a single line. While we're here, round millisecond
timings to whole ms — the only field that came through with
sub-ms precision was the new recalc duration ("17.099 ms"),
which is noise at this scale.
Co-authored-by: Claude Opus 4.7 (1M context) 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
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.
The blocking counters used to read like single-word measurements
("Render blocking" / "Potentially blocking"), making it ambiguous
whether the number was milliseconds, bytes, or something else.
Spell out that they're request counts. Move the style recalc rows
above them so the actual work (elements touched / time spent)
reads first and the per-class request totals follow as context.
Tighten the recalc labels so the longest one fits the metric
column on a single line. While we're here, round millisecond
timings to whole ms — the only field that came through with
sub-ms precision was the new recalc duration ("17.099 ms"),
which is noise at this scale.
Co-authored-by: Claude Opus 4.7 (1M context) noreply@anthropic.com