Experiment: Run the Tag Processor on every tag on output. #5662
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.
Using this to get a baseline measurement on a kind of "worst case" scenario with the HTML Tag Processor: how much delay do we incur if we're running the processor over the final page output and processing every tag?
Why would this be useful information or a useful practice?
srcset
values in one final goid
valuesIn this experiment every
src
andhref
attribute value is parsed.Initial results
twentytwentyfour
's homepagetwentytwentyfour
homepage, the speed improvement probably due to the large inline stylesheet on the pageFrom my estimates this should be adding around at least 1ms of page render time, but we aren't able to statistically infer that from the results. Why this is I'm not sure because I would expect a 1% change to certainly appear, but something else might be masking the impact.