|
| 1 | +exports[`Trace parsing > can format results of a trace 1`] = ` |
| 2 | +URL: https://web.dev/ |
| 3 | +Bounds: {min: 122410994891, max: 122416385853} |
| 4 | +CPU throttling: none |
| 5 | +Network throttling: none |
| 6 | +Metrics (lab / observed): |
| 7 | + - LCP: 129 ms, event: (eventKey: r-6063, ts: 122411126100) |
| 8 | + - LCP breakdown: |
| 9 | + - TTFB: 7.9 ms, bounds: {min: 122410996889, max: 122411004828} |
| 10 | + - Load delay: 33.2 ms, bounds: {min: 122411004828, max: 122411037986} |
| 11 | + - Load duration: 14.7 ms, bounds: {min: 122411037986, max: 122411052690} |
| 12 | + - Render delay: 73.4 ms, bounds: {min: 122411052690, max: 122411126100} |
| 13 | + - CLS: 0.00 |
| 14 | +Available insights: |
| 15 | + - insight name: LCPBreakdown |
| 16 | + 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. |
| 17 | + relevant trace bounds: {min: 122410996889, max: 122411126100} |
| 18 | + example question: Help me optimize my LCP score |
| 19 | + example question: Which LCP phase was most problematic? |
| 20 | + example question: What can I do to reduce the LCP time for this page load? |
| 21 | + - insight name: LCPDiscovery |
| 22 | + 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) |
| 23 | + relevant trace bounds: {min: 122411004828, max: 122411055039} |
| 24 | + example question: Suggest fixes to reduce my LCP |
| 25 | + example question: What can I do to reduce my LCP discovery time? |
| 26 | + example question: Why is LCP discovery time important? |
| 27 | + - insight name: RenderBlocking |
| 28 | + 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. |
| 29 | + relevant trace bounds: {min: 122411037528, max: 122411053852} |
| 30 | + example question: Show me the most impactful render blocking requests that I should focus on |
| 31 | + example question: How can I reduce the number of render blocking requests? |
| 32 | + - insight name: DocumentLatency |
| 33 | + description: Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression. |
| 34 | + relevant trace bounds: {min: 122410998910, max: 122411043781} |
| 35 | + estimated metric savings: FCP 0 ms, LCP 0 ms |
| 36 | + estimated wasted bytes: 77.1 kB |
| 37 | + example question: How do I decrease the initial loading time of my page? |
| 38 | + example question: Did anything slow down the request for this document? |
| 39 | + - insight name: ThirdParties |
| 40 | + 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. |
| 41 | + relevant trace bounds: {min: 122411037881, max: 122416229595} |
| 42 | + example question: Which third parties are having the largest impact on my page performance? |
| 43 | +`; |
0 commit comments