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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
core(lantern): always use flexible network ordering #14612
core(lantern): always use flexible network ordering #14612
Changes from 11 commits
538ed45
05b225f
7bffa76
7c182f8
53e50d4
910894b
57c1716
785b7b6
32502ad
5af3672
7816de0
ff03edc
a8c9bc7
be4a82b
ecbfeb3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: verify this or change test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
const {nodeTimings} = simulator.simulate(fcpGraph);
inrender-blocking-resources.js estimateSavingsWithGraphs
gives2884
for script.js, whereas before it was2100
. AFAICT no other numbers in this method varied. This is enough to make the "before inline" FCP estimate always be higher than the "after inline" estimate for this trace.The test does otherwise fail if we comment out the amp-specific handling in render-blocking-resources.js, and I think the change in the FCP estimate is to be expected from this PR, so updating to 0 here seems the approach to take.