Chrome DevTools MCP

exports[`performance > performance_analyze_insight > returns the information on the insight 1`] = ` ## Insight Title: LCP breakdown ## Insight Summary: This insight is used to analyze the time spent that contributed to the final LCP time and identify which of the 4 phases (or 2 if there was no LCP resource) are contributing most to the delay in rendering the LCP element. ## Detailed analysis: The Largest Contentful Paint (LCP) time for this navigation was 129 ms. The LCP element is an image fetched from \`https://web-dev.imgix.net/image/kheDArv5csY6rvQUJDbWRscckLr1/4i7JstVZvgTFk9dxCe4a.svg\`. ## LCP resource network request: https://web-dev.imgix.net/image/kheDArv5csY6rvQUJDbWRscckLr1/4i7JstVZvgTFk9dxCe4a.svg Timings: - Queued at: 41 ms - Request sent at: 47 ms - Download complete at: 56 ms - Main thread processing completed at: 58 ms Durations: - Download time: 0.3 ms - Main thread processing time: 2 ms - Total duration: 17 ms Redirects: no redirects Status code: 200 MIME Type: image/svg+xml Protocol: unknown Priority: VeryHigh Render blocking: No From a service worker: No Initiators (root request to the request that directly loaded this one): none We can break this time down into the 4 phases that combine to make the LCP time: - Time to first byte: 8 ms (6.1% of total LCP time) - Resource load delay: 33 ms (25.7% of total LCP time) - Resource load duration: 15 ms (11.4% of total LCP time) - Element render delay: 73 ms (56.8% of total LCP time) ## Estimated savings: none ## External resources: - https://web.dev/articles/lcp - https://web.dev/articles/optimize-lcp `; exports[`performance > performance_stop_trace > returns an error message if parsing the trace buffer fails 1`] = ` The performance trace has been stopped. There was an unexpected error parsing the trace: No buffer was provided. `; exports[`performance > performance_stop_trace > returns the high level summary of the performance trace 1`] = ` The performance trace has been stopped. Here is a high level summary of the trace and the Insights that were found: 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: 8 ms, bounds: {min: 122410996889, max: 122411004828} - Load delay: 33 ms, bounds: {min: 122411004828, max: 122411037986} - Load duration: 15 ms, bounds: {min: 122411037986, max: 122411052690} - Render delay: 73 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? `;