-
Notifications
You must be signed in to change notification settings - Fork 987
feat: use Performance Trace Formatter in trace output #36
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| exports[`Trace parsing > can format results of a trace 1`] = ` | ||
| URL: https://web.dev/ | ||
| Bounds: {min: 122410994891, max: 122416385853} | ||
| CPU throttling: none | ||
| Network throttling: none | ||
| Metrics (lab / observed): | ||
| - LCP: 129 ms, event: (eventKey: r-6063, ts: 122411126100) | ||
| - LCP breakdown: | ||
| - TTFB: 7.9 ms, bounds: {min: 122410996889, max: 122411004828} | ||
| - Load delay: 33.2 ms, bounds: {min: 122411004828, max: 122411037986} | ||
| - Load duration: 14.7 ms, bounds: {min: 122411037986, max: 122411052690} | ||
| - Render delay: 73.4 ms, bounds: {min: 122411052690, max: 122411126100} | ||
| - CLS: 0.00 | ||
| Metrics (field / real users): n/a – no data for this page in CrUX | ||
| Available insights: | ||
| - insight name: LCPBreakdown | ||
| description: Each [subpart has specific improvement strategies](https://web.dev/articles/optimize-lcp#lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays. | ||
| relevant trace bounds: {min: 122410996889, max: 122411126100} | ||
| example question: Help me optimize my LCP score | ||
| example question: Which LCP phase was most problematic? | ||
| example question: What can I do to reduce the LCP time for this page load? | ||
| - insight name: LCPDiscovery | ||
| description: Optimize LCP by making the LCP image [discoverable](https://web.dev/articles/optimize-lcp#1_eliminate_resource_load_delay) from the HTML immediately, and [avoiding lazy-loading](https://web.dev/articles/lcp-lazy-loading) | ||
| relevant trace bounds: {min: 122411004828, max: 122411055039} | ||
| example question: Suggest fixes to reduce my LCP | ||
| example question: What can I do to reduce my LCP discovery time? | ||
| example question: Why is LCP discovery time important? | ||
| - insight name: RenderBlocking | ||
| description: Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources) can move these network requests out of the critical path. | ||
| relevant trace bounds: {min: 122411037528, max: 122411053852} | ||
| example question: Show me the most impactful render blocking requests that I should focus on | ||
| example question: How can I reduce the number of render blocking requests? | ||
| - insight name: DocumentLatency | ||
| description: Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression. | ||
| relevant trace bounds: {min: 122410998910, max: 122411043781} | ||
| estimated metric savings: FCP 0 ms, LCP 0 ms | ||
| estimated wasted bytes: 77.1 kB | ||
| example question: How do I decrease the initial loading time of my page? | ||
| example question: Did anything slow down the request for this document? | ||
| - insight name: ThirdParties | ||
| description: 3rd party code can significantly impact load performance. [Reduce and defer loading of 3rd party code](https://web.dev/articles/optimizing-content-efficiency-loading-third-party-javascript/) to prioritize your page's content. | ||
| relevant trace bounds: {min: 122411037881, max: 122416229595} | ||
| example question: Which third parties are having the largest impact on my page performance? | ||
| `; |
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.