chrome-devtools-frontend 1.0.1473514 → 1.0.1510180

package/front_end/models/ai_assistance/data_formatters/PerformanceInsightFormatter.snapshot.txt

@@ -0,0 +1,890 @@
+Title: PerformanceInsightFormatter formats correctly when the LCP image has nodeName
+Content:
+## 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 239.8 ms.
+The LCP element (IMG) is an image fetched from `https://creativetouchrotherham.co.uk/images/creative-touch-home/creative_touch_rotherham_homehero/creative_touch_rotherham_homehero_700.webp`.
+## LCP resource network request: https://creativetouchrotherham.co.uk/images/creative-touch-home/creative_touch_rotherham_homehero/creative_touch_rotherham_homehero_700.webp
+Timings:
+- Queued at: 54.6 ms
+- Request sent at: 60.1 ms
+- Download complete at: 220.2 ms
+- Main thread processing completed at: 220.5 ms
+Durations:
+- Download time: 8.6 ms
+- Main thread processing time: 0.2 ms
+- Total duration: 165.9 ms
+Initiator: file:///Users/cjamcl/surge/misc/display-dpr/index.html
+Redirects: no redirects
+Status code: 200
+MIME Type: image/webp
+Protocol: h2
+Priority: High
+Render blocking: No
+From a service worker: No
+Initiators (root request to the request that directly loaded this one): file:///Users/cjamcl/surge/misc/display-dpr/index.html
+Response headers
+- cache-control: max-age=31536000, public
+- x-via: <redacted>
+- etag: <redacted>
+- x-guest-hostname: <redacted>
+- access-control-allow-methods: *
+- expires: Wed, 08 Jul 2026 17:27:17 GMT
+- x-cdn-cache-status: <redacted>
+- accept-ranges: bytes
+- x-static-config: <redacted>
+- content-length: <redacted>
+- date: Tue, 08 Jul 2025 17:27:29 GMT
+- content-type: image/webp
+- last-modified: Mon, 27 Jan 2025 17:50:34 GMT
+- server: Apache
+- access-control-allow-headers: Origin, X-Requested-With, Content-Type, Accept, Authorization
+
+We can break this time down into the 4 phases that combine to make the LCP time:
+
+- Time to first byte: 1.6 ms (0.7% of total LCP time)
+- Resource load delay: 53.0 ms (22.1% of total LCP time)
+- Resource load duration: 165.7 ms (69.1% of total LCP time)
+- Element render delay: 19.6 ms (8.2% of total LCP time)
+
+## Estimated savings: none
+
+## External resources:
+- https://web.dev/articles/lcp
+- https://web.dev/articles/optimize-lcp
+=== end content
+
+Title: PerformanceInsightFormatter LCP breakdown serializes the correct details
+Content:
+## 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.2 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.1 ms
+- Request sent at: 46.6 ms
+- Download complete at: 55.8 ms
+- Main thread processing completed at: 58.2 ms
+Durations:
+- Download time: 0.3 ms
+- Main thread processing time: 2.3 ms
+- Total duration: 17.1 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: 7.9 ms (6.1% of total LCP time)
+- Resource load delay: 33.2 ms (25.7% of total LCP time)
+- Resource load duration: 14.7 ms (11.4% of total LCP time)
+- Element render delay: 73.4 ms (56.8% of total LCP time)
+
+## Estimated savings: none
+
+## External resources:
+- https://web.dev/articles/lcp
+- https://web.dev/articles/optimize-lcp
+=== end content
+
+Title: PerformanceInsightFormatter LCP breakdown formats correctly when the LCP is text based and has no load delay or time phases
+Content:
+## 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 106.5 ms.
+The LCP element is text and was not fetched from the network.
+
+We can break this time down into the 2 phases that combine to make the LCP time:
+
+- Time to first byte: 6.1 ms (5.7% of total LCP time)
+- Element render delay: 100.4 ms (94.3% of total LCP time)
+
+## Estimated savings: none
+
+## External resources:
+- https://web.dev/articles/lcp
+- https://web.dev/articles/optimize-lcp
+=== end content
+
+Title: PerformanceInsightFormatter Render blocking requests tells the LLM if there are no render blocking requests
+Content:
+## Insight Title: Render blocking requests
+
+## Insight Summary:
+This insight identifies network requests that were render blocking. Render blocking requests are impactful because they are deemed critical to the page and therefore the browser stops rendering the page until it has dealt with these resources. For this insight make sure you fully inspect the details of each render blocking network request and prioritize your suggestions to the user based on the impact of each render blocking request.
+
+## Detailed analysis:
+There are no network requests that are render blocking.
+
+## Estimated savings: FCP 0 ms, LCP 0 ms
+
+## External resources:
+- https://web.dev/articles/lcp
+- https://web.dev/articles/optimize-lcp
+=== end content
+
+Title: PerformanceInsightFormatter Render blocking requests serializes the correct details
+Content:
+## Insight Title: Render blocking requests
+
+## Insight Summary:
+This insight identifies network requests that were render blocking. Render blocking requests are impactful because they are deemed critical to the page and therefore the browser stops rendering the page until it has dealt with these resources. For this insight make sure you fully inspect the details of each render blocking network request and prioritize your suggestions to the user based on the impact of each render blocking request.
+
+## Detailed analysis:
+Here is a list of the network requests that were render blocking on this page and their duration:
+
+
+Network requests data:
+
+
+
+allUrls = [0: https://code.jquery.com/jquery-3.7.1.js, 1: http://localhost:8000/, 2: http://localhost:8000/render-blocking-stylesheet.css, 3: http://localhost:8000/render-blocking-script.js]
+
+0;581.4 ms;584.5 ms;1,942.7 ms;1,944.1 ms;1,362.7 ms;775.5 ms;1.3 ms;200;application/javascript;High;High;High;t;h2;f;1;[];[content-encoding: gzip|etag: <redacted>|age: 3975412|x-cache: <redacted>|date: Fri, 07 Mar 2025 15:02:28 GMT|content-type: application/javascript; charset=utf-8|vary: Accept-Encoding|x-cache-hits: <redacted>|last-modified: Fri, 18 Oct 1991 12:00:00 GMT|x-served-by: <redacted>|cache-control: public, max-age=31536000, stale-while-revalidate=604800|x-timer: <redacted>|via: 1.1 varnish, 1.1 varnish|accept-ranges: bytes|access-control-allow-origin: *|content-length: <redacted>|server: nginx]
+2;581.6 ms;583.1 ms;1,192.9 ms;1,193.2 ms;611.6 ms;0.2 ms;0.2 ms;200;text/css;VeryHigh;VeryHigh;VeryHigh;t;http/1.0;f;1;[];[Content-Length: <redacted>|Date: Fri, 07 Mar 2025 15:02:28 GMT|Content-type: text/css|Last-Modified: Fri, 07 Mar 2025 14:58:07 GMT|Server: SimpleHTTP/0.6 Python/3.9.6]
+3;581.6 ms;583.3 ms;1,176.6 ms;1,177.9 ms;596.3 ms;0.4 ms;1.3 ms;200;text/javascript;High;High;High;t;http/1.0;f;1;[];[Content-Length: <redacted>|Date: Fri, 07 Mar 2025 15:02:28 GMT|Content-type: text/javascript|Last-Modified: Fri, 07 Mar 2025 15:00:28 GMT|Server: SimpleHTTP/0.6 Python/3.9.6]
+
+## Estimated savings: FCP 2015 ms, LCP 0 ms
+
+## External resources:
+- https://web.dev/articles/lcp
+- https://web.dev/articles/optimize-lcp
+=== end content
+
+Title: PerformanceInsightFormatter LCP Request discovery serializes the correct details
+Content:
+## Insight Title: LCP request discovery
+
+## Insight Summary:
+This insight analyzes the time taken to discover the LCP resource and request it on the network. It only applies if the LCP element was a resource like an image that has to be fetched over the network. There are 3 checks this insight makes:
+1. Did the resource have `fetchpriority=high` applied?
+2. Was the resource discoverable in the initial document, rather than injected from a script or stylesheet?
+3. The resource was not lazy loaded as this can delay the browser loading the resource.
+
+It is important that all of these checks pass to minimize the delay between the initial page load and the LCP resource being loaded.
+
+## Detailed analysis:
+The Largest Contentful Paint (LCP) time for this navigation was 1,077.1 ms.
+The LCP element is an image fetched from `http://localhost:8787/lcp-discovery-delay/lcp-image.jpg`.
+## LCP resource network request: http://localhost:8787/lcp-discovery-delay/lcp-image.jpg
+Timings:
+- Queued at: 1,010.1 ms
+- Request sent at: 1,011.5 ms
+- Download complete at: 1,013.7 ms
+- Main thread processing completed at: 1,016.9 ms
+Durations:
+- Download time: 1.0 ms
+- Main thread processing time: 3.2 ms
+- Total duration: 6.8 ms
+Initiator: http://localhost:8787/lcp-discovery-delay/index.html
+Redirects: no redirects
+Status code: 200
+MIME Type: image/jpeg
+Protocol: http/1.1
+Initial priority: Low
+Final priority: High
+Render blocking: No
+From a service worker: No
+Initiators (root request to the request that directly loaded this one): http://localhost:8787/lcp-discovery-delay/index.html
+Response headers
+- Cache-Control: public, max-age=0
+- ETag: <redacted>
+- Connection: keep-alive
+- Accept-Ranges: bytes
+- Content-Length: <redacted>
+- Keep-Alive: <redacted>
+- Date: Tue, 18 Feb 2025 11:23:05 GMT
+- Last-Modified: Tue, 18 Feb 2025 11:21:06 GMT
+- Content-Type: image/jpeg
+
+The result of the checks for this insight are:
+- fetchpriority=high should be applied: FAILED
+- lazy load not applied: PASSED
+- Request is discoverable in initial document: PASSED
+
+## Estimated savings: none
+
+## External resources:
+- https://web.dev/articles/lcp
+- https://web.dev/articles/optimize-lcp
+=== end content
+
+Title: PerformanceInsightFormatter Document request latency serializes the correct details
+Content:
+## Insight Title: Document request latency
+
+## Insight Summary:
+This insight checks that the first request is responded to promptly. We use the following criteria to check this:
+1. Was the initial request redirected?
+2. Did the server respond in 600ms or less? We want developers to aim for as close to 100ms as possible, but our threshold for this insight is 600ms.
+3. Was there compression applied to the response to minimize the transfer size?
+
+## Detailed analysis:
+The Largest Contentful Paint (LCP) time for this navigation was 3,604.1 ms.
+The LCP element is text and was not fetched from the network.
+
+## Document network request: http://localhost:3000/redirect3
+Timings:
+- Queued at: 3.0 ms
+- Request sent at: 1,529.5 ms
+- Download complete at: 3,532.6 ms
+- Main thread processing completed at: 3,537.8 ms
+Durations:
+- Download time: 0.1 ms
+- Main thread processing time: 5.1 ms
+- Total duration: 3,534.7 ms
+Redirects:
+#### Redirect 1: http://localhost:3000/
+- Start time: 3.0 ms
+- Duration: 512.0 ms
+#### Redirect 2: http://localhost:3000/redirect1
+- Start time: 515.1 ms
+- Duration: 505.7 ms
+#### Redirect 3: http://localhost:3000/redirect2
+- Start time: 1,020.7 ms
+- Duration: 507.1 ms
+Status code: 200
+MIME Type: text/html
+Protocol: http/1.1
+Priority: VeryHigh
+Render blocking: No
+From a service worker: No
+Initiators (root request to the request that directly loaded this one): none
+Response headers
+- Transfer-Encoding: chunked
+- Keep-Alive: <redacted>
+- Date: Tue, 11 Mar 2025 10:19:12 GMT
+- Content-Type: text/html
+- Connection: keep-alive
+
+The result of the checks for this insight are:
+- The request was not redirected: FAILED
+- Server responded quickly: FAILED
+- Compression was applied: FAILED
+
+## Estimated savings: FCP 3428 ms, LCP 3428 ms
+
+## External resources:
+- https://web.dev/articles/optimize-ttfb
+=== end content
+
+Title: PerformanceInsightFormatter CLS serializes the correct details
+Content:
+## Insight Title: Layout shift culprits
+
+## Insight Summary:
+Cumulative Layout Shifts (CLS) is a measure of the largest burst of layout shifts for every unexpected layout shift that occurs during the lifecycle of a page. This is a Core Web Vital and the thresholds for categorizing a score are:
+- Good: 0.1 or less
+- Needs improvement: more than 0.1 and less than or equal to 0.25
+- Bad: over 0.25
+
+## Detailed analysis:
+The worst layout shift cluster was the cluster that started at 471.8 ms and ended at 3,342.8 ms, with a duration of 2,871.1 ms.
+The score for this cluster is 0.7656.
+
+Layout shifts in this cluster:
+### Layout shift 1:
+- Start time: 471.8 ms
+- Score: 0.0003
+- Potential root causes:
+  - A font that was loaded over the network (https://fonts.gstatic.com/s/specialgothicexpandedone/v2/IurO6Zxk74-YaYk1r3HOet4g75ENmBxUmOK61tA0Iu5QmJF_.woff2).
+### Layout shift 2:
+- Start time: 857.3 ms
+- Score: 0.0844
+- Potential root causes:
+  - An iframe (id: 8AF3A9ADB81CA7B35302D07E0B591104, url: https://www.google.com/ was injected into the page)
+### Layout shift 3:
+- Start time: 1,352.5 ms
+- Score: 0.0068
+- Potential root causes:
+  - An unsized image (IMG) (url: http://localhost:8000/unsized-image.png).
+### Layout shift 4:
+- Start time: 1,537.5 ms
+- Score: 0.3344
+- Potential root causes:
+  - An unsized image (IMG) (url: http://localhost:8000/unsized-image.png).
+### Layout shift 5:
+- Start time: 2,342.8 ms
+- Score: 0.3396
+- No potential root causes identified
+
+## Estimated savings: none
+
+## External resources:
+- https://wdeb.dev/articles/cls
+- https://web.dev/articles/optimize-cls
+=== end content
+
+Title: PerformanceInsightFormatter INP breakdown serializes the correct details
+Content:
+## Insight Title: INP breakdown
+
+## Insight Summary:
+Interaction to Next Paint (INP) is a metric that tracks the responsiveness of the page when the user interacts with it. INP is a Core Web Vital and the thresholds for how we categorize a score are:
+- Good: 200 milliseconds or less.
+- Needs improvement: more than 200 milliseconds and 500 milliseconds or less.
+- Bad: over 500 milliseconds.
+
+For a given slow interaction, we can break it down into 3 phases:
+1. Input delay: starts when the user initiates an interaction with the page, and ends when the event callbacks for the interaction begin to run.
+2. Processing duration: the time it takes for the event callbacks to run to completion.
+3. Presentation delay: the time it takes for the browser to present the next frame which contains the visual result of the interaction.
+
+The sum of these three phases is the total latency. It is important to optimize each of these phases to ensure interactions take as little time as possible. Focusing on the phase that has the largest score is a good way to start optimizing.
+
+## Detailed analysis:
+The longest interaction on the page was a `click` which had a total duration of `980.0 ms`. The timings of each of the three phases were:
+
+1. Input delay: 1.0 ms
+2. Processing duration: 977.0 ms
+3. Presentation delay: 2.0 ms.
+
+## Estimated savings: none
+
+## External resources:
+- https://web.dev/articles/inp
+- https://web.dev/explore/how-to-optimize-inp
+- https://web.dev/articles/optimize-long-tasks
+- https://web.dev/articles/avoid-large-complex-layouts-and-layout-thrashing
+=== end content
+
+Title: PerformanceInsightFormatter ModernHTTP serializes the correct details when no requests are using legacy http
+Content:
+## Insight Title: Modern HTTP
+
+## Insight Summary:
+Modern HTTP protocols, such as HTTP/2, are more efficient than older versions like HTTP/1.1 because they allow for multiple requests and responses to be sent over a single network connection, significantly improving page load performance by reducing latency and overhead. This insight identifies requests that can be upgraded to a modern HTTP protocol.
+
+We apply a conservative approach when flagging HTTP/1.1 usage. This insight will only flag requests that meet all of the following criteria:
+1.  Were served over HTTP/1.1 or an earlier protocol.
+2.  Originate from an origin that serves at least 6 static asset requests, as the benefits of multiplexing are less significant with fewer requests.
+3.  Are not served from 'localhost' or coming from a third-party source, where developers have no control over the server's protocol.
+
+To pass this insight, ensure your server supports and prioritizes a modern HTTP protocol (like HTTP/2) for static assets, especially when serving a substantial number of them.
+
+## Detailed analysis:
+There are no requests that were served over a legacy HTTP protocol.
+
+## Estimated savings: none
+
+## External resources:
+- https://developer.chrome.com/docs/lighthouse/best-practices/uses-http2
+=== end content
+
+Title: PerformanceInsightFormatter ModernHTTP serializes the correct details when requests are using legacy http
+Content:
+## Insight Title: Modern HTTP
+
+## Insight Summary:
+Modern HTTP protocols, such as HTTP/2, are more efficient than older versions like HTTP/1.1 because they allow for multiple requests and responses to be sent over a single network connection, significantly improving page load performance by reducing latency and overhead. This insight identifies requests that can be upgraded to a modern HTTP protocol.
+
+We apply a conservative approach when flagging HTTP/1.1 usage. This insight will only flag requests that meet all of the following criteria:
+1.  Were served over HTTP/1.1 or an earlier protocol.
+2.  Originate from an origin that serves at least 6 static asset requests, as the benefits of multiplexing are less significant with fewer requests.
+3.  Are not served from 'localhost' or coming from a third-party source, where developers have no control over the server's protocol.
+
+To pass this insight, ensure your server supports and prioritizes a modern HTTP protocol (like HTTP/2) for static assets, especially when serving a substantial number of them.
+
+## Detailed analysis:
+Here is a list of the network requests that were served over a legacy HTTP protocol:
+
+Network requests data:
+
+
+
+allUrls = [0: https://ads.jetpackdigital.com/sites/_uploads/1742278386bg_opt_640x350-avif.avif, 1: http://localhost/old-http.html, 2: https://ads.jetpackdigital.com/sites/_uploads/1583540859Play.png, 3: https://ads.jetpackdigital.com/sites/_uploads/1583540859Muted.png, 4: https://ads.jetpackdigital.com/h5media/sites/_uploads/1742363510mm_allthefeels_20_mob.mp4, 5: https://ads.jetpackdigital.com/sites/_uploads/1583540860Pause.png, 6: https://ads.jetpackdigital.com/tracking_pixel.gif?8852762616, 7: https://ads.jetpackdigital.com/tracking_pixel.gif?7753243273]
+
+0;8.1 ms;12.4 ms;25.7 ms;25.8 ms;17.7 ms;1.6 ms;0.1 ms;200;image/avif;Low;Low;Low;f;http/1.1;f;1;[];[x-amz-id-2: <redacted>|ETag: <redacted>|Connection: keep-alive|Access-Control-Allow-Methods: GET,HEAD,POST|x-amz-request-id: <redacted>|Accept-Ranges: bytes|Access-Control-Allow-Origin: *|Content-Length: <redacted>|Date: Thu, 20 Mar 2025 19:45:22 GMT|Last-Modified: Tue, 18 Mar 2025 06:13:07 GMT|Content-Type: image/avif|Server: AmazonS3|x-amz-server-side-encryption: <redacted>]
+2;8.2 ms;12.5 ms;24.0 ms;24.3 ms;16.1 ms;0.6 ms;0.3 ms;200;image/png;Low;Low;Low;f;http/1.1;f;1;[];[x-amz-id-2: <redacted>|ETag: <redacted>|Connection: keep-alive|Access-Control-Allow-Methods: GET,HEAD,POST|x-amz-request-id: <redacted>|Accept-Ranges: bytes|Access-Control-Allow-Origin: *|Content-Length: <redacted>|Date: Thu, 20 Mar 2025 19:45:22 GMT|Last-Modified: Tue, 24 Jan 2023 19:05:17 GMT|Content-Type: image/png|Server: AmazonS3|x-amz-server-side-encryption: <redacted>]
+3;8.3 ms;12.6 ms;24.6 ms;25.0 ms;16.7 ms;1.2 ms;0.3 ms;200;image/png;Low;Low;Low;f;http/1.1;f;1;[];[x-amz-id-2: <redacted>|ETag: <redacted>|Connection: keep-alive|Access-Control-Allow-Methods: GET,HEAD,POST|x-amz-request-id: <redacted>|Accept-Ranges: bytes|Access-Control-Allow-Origin: *|Content-Length: <redacted>|Date: Thu, 20 Mar 2025 19:45:22 GMT|Last-Modified: Tue, 24 Jan 2023 19:05:17 GMT|Content-Type: image/png|Server: AmazonS3|x-amz-server-side-encryption: <redacted>]
+4;8.4 ms;12.8 ms;24.5 ms;24.5 ms;16.1 ms;0.4 ms;0.0 ms;200;video/mp4;Low;Low;Low;f;http/1.1;f;1;[];[x-amz-id-2: <redacted>|ETag: <redacted>|Connection: keep-alive|Access-Control-Allow-Methods: GET,HEAD,POST|x-amz-request-id: <redacted>|Accept-Ranges: bytes|Access-Control-Allow-Origin: *|Content-Length: <redacted>|Date: Thu, 20 Mar 2025 19:45:22 GMT|Last-Modified: Wed, 19 Mar 2025 05:51:52 GMT|Content-Type: video/mp4|Server: AmazonS3|x-amz-server-side-encryption: <redacted>]
+5;8.4 ms;12.9 ms;24.7 ms;25.0 ms;16.6 ms;1.3 ms;0.3 ms;200;image/png;Low;Low;Low;f;http/1.1;f;1;[];[x-amz-id-2: <redacted>|ETag: <redacted>|Connection: keep-alive|Access-Control-Allow-Methods: GET,HEAD,POST|x-amz-request-id: <redacted>|Accept-Ranges: bytes|Access-Control-Allow-Origin: *|Content-Length: <redacted>|Date: Thu, 20 Mar 2025 19:45:22 GMT|Last-Modified: Tue, 24 Jan 2023 19:05:18 GMT|Content-Type: image/png|Server: AmazonS3|x-amz-server-side-encryption: <redacted>]
+6;8.4 ms;24.4 ms;38.5 ms;38.7 ms;30.3 ms;0.1 ms;0.2 ms;200;image/gif;Low;Low;Low;f;http/1.1;f;1;[];[x-amz-id-2: <redacted>|x-amz-meta-jets3t-original-file-date-iso8601: <redacted>|ETag: <redacted>|x-amz-meta-md5-hash: <redacted>|Connection: keep-alive|Access-Control-Allow-Methods: GET,HEAD,POST|x-amz-request-id: <redacted>|Accept-Ranges: bytes|Access-Control-Allow-Origin: *|Content-Length: <redacted>|Date: Thu, 20 Mar 2025 19:45:22 GMT|Last-Modified: Tue, 24 Jan 2023 19:54:47 GMT|Content-Type: image/gif|Server: AmazonS3|x-amz-server-side-encryption: <redacted>]
+7;8.4 ms;24.9 ms;37.8 ms;38.0 ms;29.6 ms;0.2 ms;0.2 ms;200;image/gif;Low;Low;Low;f;http/1.1;f;1;[];[x-amz-id-2: <redacted>|x-amz-meta-jets3t-original-file-date-iso8601: <redacted>|ETag: <redacted>|x-amz-meta-md5-hash: <redacted>|Connection: keep-alive|Access-Control-Allow-Methods: GET,HEAD,POST|x-amz-request-id: <redacted>|Accept-Ranges: bytes|Access-Control-Allow-Origin: *|Content-Length: <redacted>|Date: Thu, 20 Mar 2025 19:45:22 GMT|Last-Modified: Tue, 24 Jan 2023 19:54:47 GMT|Content-Type: image/gif|Server: AmazonS3|x-amz-server-side-encryption: <redacted>]
+
+## Estimated savings: FCP 0 ms, LCP 0 ms
+
+## External resources:
+- https://developer.chrome.com/docs/lighthouse/best-practices/uses-http2
+=== end content
+
+Title: PerformanceInsightFormatter Formatting TraceEvents formats network requests in verbose mode
+Content:
+## Network request: https://fonts.googleapis.com/css2?family=Poppins:ital,wght@1,800
+Timings:
+- Queued at: 37.6 ms
+- Request sent at: 41.7 ms
+- Download complete at: 48.0 ms
+- Main thread processing completed at: 51.5 ms
+Durations:
+- Download time: 4.8 ms
+- Main thread processing time: 3.5 ms
+- Total duration: 13.9 ms
+Initiator: https://chromedevtools.github.io/performance-stories/lcp-large-image/index.html
+Redirects: no redirects
+Status code: 200
+MIME Type: text/css
+Protocol: unknown
+Priority: VeryHigh
+Render blocking: Yes
+From a service worker: No
+Initiators (root request to the request that directly loaded this one): https://chromedevtools.github.io/performance-stories/lcp-large-image/index.html
+Response headers
+- date: Thu, 07 Mar 2024 21:17:02 GMT
+- content-encoding: gzip
+- x-content-type-options: nosniff
+- last-modified: Thu, 07 Mar 2024 21:17:02 GMT
+- server: ESF
+- cross-origin-opener-policy: <redacted>
+- x-frame-options: SAMEORIGIN
+- content-type: text/css; charset=utf-8
+- access-control-allow-origin: *
+- cache-control: private, max-age=86400, stale-while-revalidate=604800
+- cross-origin-resource-policy: <redacted>
+- timing-allow-origin: *
+- link: <https://fonts.gstatic.com>; rel=preconnect; crossorigin
+- x-xss-protection: 0
+- expires: Thu, 07 Mar 2024 21:17:02 GMT
+=== end content
+
+Title: PerformanceInsightFormatter Formatting TraceEvents defaults to verbose mode when 1 request and verbose option is not defined
+Content:
+## Network request: https://fonts.googleapis.com/css2?family=Poppins:ital,wght@1,800
+Timings:
+- Queued at: 37.6 ms
+- Request sent at: 41.7 ms
+- Download complete at: 48.0 ms
+- Main thread processing completed at: 51.5 ms
+Durations:
+- Download time: 4.8 ms
+- Main thread processing time: 3.5 ms
+- Total duration: 13.9 ms
+Initiator: https://chromedevtools.github.io/performance-stories/lcp-large-image/index.html
+Redirects: no redirects
+Status code: 200
+MIME Type: text/css
+Protocol: unknown
+Priority: VeryHigh
+Render blocking: Yes
+From a service worker: No
+Initiators (root request to the request that directly loaded this one): https://chromedevtools.github.io/performance-stories/lcp-large-image/index.html
+Response headers
+- date: Thu, 07 Mar 2024 21:17:02 GMT
+- content-encoding: gzip
+- x-content-type-options: nosniff
+- last-modified: Thu, 07 Mar 2024 21:17:02 GMT
+- server: ESF
+- cross-origin-opener-policy: <redacted>
+- x-frame-options: SAMEORIGIN
+- content-type: text/css; charset=utf-8
+- access-control-allow-origin: *
+- cache-control: private, max-age=86400, stale-while-revalidate=604800
+- cross-origin-resource-policy: <redacted>
+- timing-allow-origin: *
+- link: <https://fonts.gstatic.com>; rel=preconnect; crossorigin
+- x-xss-protection: 0
+- expires: Thu, 07 Mar 2024 21:17:02 GMT
+=== end content
+
+Title: PerformanceInsightFormatter Duplicated javascript serializes the correct details
+Content:
+## Insight Title: Duplicated JavaScript
+
+## Insight Summary:
+This insight identifies large, duplicated JavaScript modules that are present in your application and create redundant code.
+  This wastes network bandwidth and slows down your page, as the user's browser must download and process the same code multiple times.
+
+## Detailed analysis:
+Total wasted bytes: 615821 bytes.
+
+Duplication grouped by Node modules: - Source: node_modules/filestack-js - Duplicated bytes: 345779 bytes
+- Source: node_modules/@headlessui/react - Duplicated bytes: 46023 bytes
+- Source: node_modules/react-query - Duplicated bytes: 32976 bytes
+- Source: node_modules/@floating-ui/react-dom-interactions - Duplicated bytes: 26253 bytes
+- Source: node_modules/yup - Duplicated bytes: 22581 bytes
+- Source: node_modules/lodash - Duplicated bytes: 21453 bytes
+- Source: node_modules/@formatjs/icu-messageformat-parser - Duplicated bytes: 20835 bytes
+- Source: node_modules/react-hook-form - Duplicated bytes: 17328 bytes
+- Source: node_modules/@popperjs/core - Duplicated bytes: 15900 bytes
+- Source: node_modules/downshift - Duplicated bytes: 14925 bytes
+- Source: node_modules/axios - Duplicated bytes: 14079 bytes
+- Source: node_modules/react-dropzone - Duplicated bytes: 12180 bytes
+- Source: node_modules/@formatjs/intl - Duplicated bytes: 10839 bytes
+- Source: node_modules/qs - Duplicated bytes: 9210 bytes
+- Source: node_modules/object-inspect - Duplicated bytes: 7254 bytes
+- Source: node_modules/history - Duplicated bytes: 6870 bytes
+- Source: node_modules/@heroicons/react - Duplicated bytes: 6624 bytes
+- Source: node_modules/react-intl - Duplicated bytes: 6534 bytes
+- Source: node_modules/get-intrinsic - Duplicated bytes: 6411 bytes
+- Source: node_modules/@floating-ui/dom - Duplicated bytes: 6147 bytes
+- Source: node_modules/@formatjs/icu-skeleton-parser - Duplicated bytes: 5736 bytes
+- Source: webpack://ssi/src/components/Autocomplete/Autocomplete.tsx - Duplicated bytes: 5721 bytes
+- Source: node_modules/@floating-ui/core - Duplicated bytes: 5661 bytes
+- Source: node_modules/intl-messageformat - Duplicated bytes: 5583 bytes
+- Source: node_modules/@loadable/component - Duplicated bytes: 4482 bytes
+- Source: node_modules/file-selector - Duplicated bytes: 4374 bytes
+- Source: node_modules/universal-cookie - Duplicated bytes: 4191 bytes
+- Source: node_modules/tabbable - Duplicated bytes: 4146 bytes
+- Source: webpack://ssi/src/components/Button/Button.tsx - Duplicated bytes: 3711 bytes
+- Source: node_modules/path-to-regexp - Duplicated bytes: 2865 bytes
+- Source: webpack://ssi/src/components/Link/Link.tsx - Duplicated bytes: 2766 bytes
+- Source: node_modules/isomorphic-style-loader - Duplicated bytes: 2520 bytes
+- Source: webpack://ssi/src/components/Menu/MenuBase.tsx - Duplicated bytes: 2415 bytes
+- Source: node_modules/tslib - Duplicated bytes: 2376 bytes
+- Source: node_modules/compute-scroll-into-view - Duplicated bytes: 2166 bytes
+- Source: node_modules/react-router-dom - Duplicated bytes: 2154 bytes
+- Source: node_modules/react-fast-compare - Duplicated bytes: 1935 bytes
+- Source: node_modules/react-is - Duplicated bytes: 1845 bytes
+- Source: node_modules/react-router - Duplicated bytes: 1788 bytes
+- Source: node_modules/css-loader - Duplicated bytes: 1608 bytes
+- Source: node_modules/mini-create-react-context - Duplicated bytes: 1563 bytes
+
+## Estimated savings: FCP 100 ms, LCP 100 ms
+
+## External resources:
+=== end content
+
+Title: PerformanceInsightFormatter Duplicated javascript serializes no details if there is no duplicate javascript
+Content:
+## Insight Title: Duplicated JavaScript
+
+## Insight Summary:
+This insight identifies large, duplicated JavaScript modules that are present in your application and create redundant code.
+  This wastes network bandwidth and slows down your page, as the user's browser must download and process the same code multiple times.
+
+## Detailed analysis:
+There is no duplicated JavaScript in the page modules
+
+## Estimated savings: none
+
+## External resources:
+=== end content
+
+Title: PerformanceInsightFormatter Legacy JavaScript serializes the correct details when there is no legacy javascript in modules
+Content:
+## Insight Title: Legacy JavaScript
+
+## Insight Summary:
+This insight identified legacy JavaScript in your application's modules that may be creating unnecessary code.
+
+Polyfills and transforms enable older browsers to use new JavaScript features. However, many are not necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers.
+
+## Detailed analysis:
+There is no significant amount of legacy JavaScript on the page.
+
+## Estimated savings: none
+
+## External resources:
+- https://web.dev/articles/baseline-and-polyfills
+- https://philipwalton.com/articles/the-state-of-es5-on-the-web/
+=== end content
+
+Title: PerformanceInsightFormatter Legacy JavaScript serializes the correct details when modules contain legacy javascript
+Content:
+## Insight Title: Legacy JavaScript
+
+## Insight Summary:
+This insight identified legacy JavaScript in your application's modules that may be creating unnecessary code.
+
+Polyfills and transforms enable older browsers to use new JavaScript features. However, many are not necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers.
+
+## Detailed analysis:
+Total legacy JavaScript: 8 files.
+
+Legacy JavaScript by file:
+
+- Script: https://s.yimg.com/aaq/benji/benji-2.2.99.js - Wasted bytes: 37204 bytes
+Matches:
+Line: 0, Column: 133, Name: Promise.allSettled
+
+- Script: https://s.yimg.com/aaq/c/25fa214.caas-news_web.min.js - Wasted bytes: 36084 bytes
+Matches:
+Line: 0, Column: 13310, Name: Array.from
+Line: 0, Column: 14623, Name: Object.assign
+
+- Script: https://s.yimg.com/du/ay/wnsrvbjmeprtfrnfx.js - Wasted bytes: 12850 bytes
+Matches:
+Line: 111, Column: 7829, Name: @babel/plugin-transform-spread
+Line: 111, Column: 1794, Name: Array.prototype.find
+Line: 111, Column: 2127, Name: Array.prototype.includes
+Line: 111, Column: 2748, Name: Object.values
+Line: 111, Column: 2473, Name: String.prototype.includes
+Line: 111, Column: 2627, Name: String.prototype.startsWith
+
+- Script: https://static.criteo.net/js/ld/publishertag.prebid.144.js - Wasted bytes: 10751 bytes
+Matches:
+Line: 1, Column: 74871, Name: Array.isArray
+Line: 1, Column: 75344, Name: Array.prototype.filter
+Line: 1, Column: 75013, Name: Array.prototype.indexOf
+
+- Script: https://s.yimg.com/oa/consent.js - Wasted bytes: 8157 bytes
+Matches:
+Line: 1, Column: 132267, Name: Array.prototype.includes
+
+- Script: https://pm-widget.taboola.com/yahooweb-network/pmk-20220605.1.js - Wasted bytes: 7625 bytes
+Matches:
+Line: 181, Column: 26, Name: Object.keys
+
+- Script: https://news.yahoo.com/ - Wasted bytes: 7141 bytes
+Matches:
+Line: 0, Column: 8382, Name: @babel/plugin-transform-classes
+Line: 0, Column: 107712, Name: Array.prototype.filter
+Line: 0, Column: 107393, Name: Array.prototype.forEach
+Line: 0, Column: 108005, Name: Array.prototype.map
+Line: 0, Column: 108358, Name: String.prototype.includes
+
+- Script: https://cdn.taboola.com/libtrc/yahooweb-network/loader.js - Wasted bytes: 7061 bytes
+Matches:
+Line: 0, Column: 390544, Name: Object.entries
+Line: 0, Column: 390688, Name: Object.values
+
+## Estimated savings: FCP 0 ms, LCP 0 ms
+
+## External resources:
+- https://web.dev/articles/baseline-and-polyfills
+- https://philipwalton.com/articles/the-state-of-es5-on-the-web/
+=== end content
+
+Title: PerformanceInsightFormatter ImageDelivery serializes the correct details when there are no optimizable images
+Content:
+## Insight Title: Improve image delivery
+
+## Insight Summary:
+This insight identifies unoptimized images that are downloaded at a much higher resolution than they are displayed. Properly sizing and compressing these assets will decrease their download time, directly improving the perceived page load time and LCP
+
+## Detailed analysis:
+There are no unoptimized images on this page.
+
+## Estimated savings: none
+
+## External resources:
+- https://developer.chrome.com/docs/lighthouse/performance/uses-optimized-images/
+=== end content
+
+Title: PerformanceInsightFormatter ImageDelivery serializes the correct details when there are images that can be optimized
+Content:
+## Insight Title: Improve image delivery
+
+## Insight Summary:
+This insight identifies unoptimized images that are downloaded at a much higher resolution than they are displayed. Properly sizing and compressing these assets will decrease their download time, directly improving the perceived page load time and LCP
+
+## Detailed analysis:
+Total potential savings: 2.0 MB
+
+The following images could be optimized:
+
+### https://images.ctfassets.net/u275ja1nivmq/6T6z40ay5GFCUtwV7DONgh/0e23606ed1692d9721ab0f39a8d8a99e/yeti_cover.jpg
+- Potential savings: 1.1 MB
+- Optimizations:
+Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size. (Est 1.1 MB)
+
+### https://raw.githubusercontent.com/GoogleChrome/lighthouse/refs/heads/main/cli/test/fixtures/dobetterweb/lighthouse-rotating.gif
+- Potential savings: 682 kB
+- Optimizations:
+Using video formats instead of GIFs can improve the download size of animated content. (Est 682 kB)
+
+### https://onlinepngtools.com/images/examples-onlinepngtools/elephant-hd-quality.png
+- Potential savings: 176 kB
+- Optimizations:
+Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size. (Est 134 kB)
+This image file is larger than it needs to be (640x436) for its displayed dimensions (200x136). Use responsive images to reduce the image download size. (Est 163 kB)
+
+### https://images.ctfassets.net/u275ja1nivmq/6T6z40ay5GFCUtwV7DONgh/0e23606ed1692d9721ab0f39a8d8a99e/yeti_cover.jpg?fm=webp
+- Potential savings: 49.8 kB
+- Optimizations:
+Increasing the image compression factor could improve this image's download size. (Est 49.8 kB)
+
+### https://raw.githubusercontent.com/GoogleChrome/lighthouse/refs/heads/main/cli/test/fixtures/byte-efficiency/lighthouse-2048x1356.webp
+- Potential savings: 41.4 kB
+- Optimizations:
+This image file is larger than it needs to be (2048x1356) for its displayed dimensions (200x132). Use responsive images to reduce the image download size. (Est 41.4 kB)
+
+## Estimated savings: FCP 0 ms, LCP 100 ms
+
+## External resources:
+- https://developer.chrome.com/docs/lighthouse/performance/uses-optimized-images/
+=== end content
+
+Title: PerformanceInsightFormatter ForcedReflow serializes correctly when there are no results
+Content:
+## Insight Title: Forced reflow
+
+## Insight Summary:
+This insight identifies forced synchronous layouts (also known as forced reflows) and layout thrashing caused by JavaScript accessing layout properties at suboptimal points in time.
+
+## Detailed analysis:
+A forced reflow occurs when JavaScript queries geometric properties (such as `offsetWidth`) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developers.google.com/web/fundamentals/performance/rendering/avoid-large-complex-layouts-and-layout-thrashing#avoid-forced-synchronous-layouts) and possible mitigations.
+
+The forced reflow checks revealed no problems.
+
+## Estimated savings: none
+
+## External resources:
+- https://developers.google.com/web/fundamentals/performance/rendering/avoid-large-complex-layouts-and-layout-thrashing#avoid-forced-synchronous-layouts
+=== end content
+
+Title: PerformanceInsightFormatter ForcedReflow serializes the correct details when there are problems found in the network dependency tree
+Content:
+## Insight Title: Forced reflow
+
+## Insight Summary:
+This insight identifies forced synchronous layouts (also known as forced reflows) and layout thrashing caused by JavaScript accessing layout properties at suboptimal points in time.
+
+## Detailed analysis:
+A forced reflow occurs when JavaScript queries geometric properties (such as `offsetWidth`) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developers.google.com/web/fundamentals/performance/rendering/avoid-large-complex-layouts-and-layout-thrashing#avoid-forced-synchronous-layouts) and possible mitigations.
+
+The forced reflow checks revealed one or more problems.
+
+The following is the top function call that caused forced reflow(s):
+
+ - (anonymous) @ https://player.aniview.com/script/6.1/player.js:6:25217
+
+Total reflow time: 26.1 ms
+
+Stack trace (including total time):
+
+ - 56.2 ms in sidemenuitemintoview @ https://www.w3schools.com/lib/w3schools_footer.js?update=20240910:383:11
+ - 4.6 ms in ko @ https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202411070102/pubads_impl.js?cb=31088843:32:197203
+ - 14.5 ms in e @ unknown location
+ - 0.1 ms in position @ https://tg1.aniview.com/api/adserver/spt?AV_TAGID=5fc0cff7da5879436d110535&AV_PUBLISHERID=5f280c598c04cd5e910ff0a1:453:30
+ - 0.7 ms in o @ https://adengine.snigelweb.com/w3schools.com/12609-1731501024324/adngin.js:0:6042
+ - 2.3 ms in [unattributed]
+ - 0.3 ms in Aq @ https://pagead2.googlesyndication.com/pagead/managed/js/activeview/current/ufs_web_display.js:273:705
+ - 0.2 ms in E @ https://player.aniview.com/script/6.1/player.js:6:21336
+ - 0.4 ms in getPlaceholderWidth @ https://player.aniview.com/script/6.1/player.js:6:38512
+ - 24.3 ms in (anonymous) @ https://player.aniview.com/script/6.1/AVmanager.js?v=1.0&type=s&pid=5f280c598c04cd5e910ff0a1:7:364165
+ - 1.8 ms in e.getAdPosition @ https://player.aniview.com/script/6.1/AVmanager.js?v=1.0&type=s&pid=5f280c598c04cd5e910ff0a1:6:104270
+ - 0.5 ms in detect_visibility_inview_1s @ unknown location
+ - 0.0 ms in (anonymous) @ https://player.aniview.com/script/6.1/AVmanager.js?v=1.0&type=s&pid=5f280c598c04cd5e910ff0a1:6:101588
+ - 0.3 ms in Wr @ https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202411070102/pubads_impl.js?cb=31088843:32:94243
+ - 0.1 ms in (anonymous) @ https://player.aniview.com/script/webm/ads.js:5:156566
+
+## Estimated savings: none
+
+## External resources:
+- https://developers.google.com/web/fundamentals/performance/rendering/avoid-large-complex-layouts-and-layout-thrashing#avoid-forced-synchronous-layouts
+=== end content
+
+Title: PerformanceInsightFormatter NetworkDependencyTree serializes correctly when there are no results
+Content:
+## Insight Title: Network dependency tree
+
+## Insight Summary:
+This insight analyzes the network dependency tree to identify:
+- The maximum critical path latency (the longest chain of network requests that the browser must download before it can render the page).
+- Whether current [preconnect] tags are appropriate, according to the following rules:
+   1. They should all be in use (no unnecessary preconnects).
+   2. All preconnects should specify cross-origin correctly.
+   3. The maximum of 4 preconnects should be respected.
+- Opportunities to add [preconnect] for a faster loading experience.
+
+## Detailed analysis:
+The network dependency tree checks revealed no problems, but optimization suggestions may be available.
+
+No rendering tasks impacted by network dependencies.
+
+no origins were preconnected.
+
+## Estimated savings: none
+
+## External resources:
+- https://web.dev/learn/performance/understanding-the-critical-path
+- https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/
+=== end content
+
+Title: PerformanceInsightFormatter NetworkDependencyTree serializes the correct details when there are problems found in the network dependency tree
+Content:
+## Insight Title: Network dependency tree
+
+## Insight Summary:
+This insight analyzes the network dependency tree to identify:
+- The maximum critical path latency (the longest chain of network requests that the browser must download before it can render the page).
+- Whether current [preconnect] tags are appropriate, according to the following rules:
+   1. They should all be in use (no unnecessary preconnects).
+   2. All preconnects should specify cross-origin correctly.
+   3. The maximum of 4 preconnects should be respected.
+- Opportunities to add [preconnect] for a faster loading experience.
+
+## Detailed analysis:
+The network dependency tree checks found one or more problems.
+
+Max critical path latency is 5,014.9 ms
+
+The following is the critical request chain:
+- http://localhost:8787/lcp-iframes/index.html (5,005.6 ms) (longest chain)
+  - http://localhost:8787/lcp-iframes/app.js (5,014.9 ms) (longest chain)
+  - http://localhost:8787/lcp-iframes/app.css (5,010.1 ms)
+
+no origins were preconnected.
+
+## Estimated savings: none
+
+## External resources:
+- https://web.dev/learn/performance/understanding-the-critical-path
+- https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/
+=== end content
+
+Title: PerformanceInsightFormatter Third Parties Insight serializes correctly when there are no results
+Content:
+## Insight Title: 3rd parties
+
+## Insight Summary:
+This insight analyzes the performance impact of resources loaded from third-party servers and aggregates the performance cost, in terms of download transfer sizes and total amount of time that third party scripts spent executing on the main thread.
+
+## Detailed analysis:
+No 3rd party scripts were found on this page.
+
+## Estimated savings: none
+
+## External resources:
+- https://web.dev/articles/optimizing-content-efficiency-loading-third-party-javascript/
+=== end content
+
+Title: PerformanceInsightFormatter Third Parties Insight serializes 3rd party scripts correctly
+Content:
+## Insight Title: 3rd parties
+
+## Insight Summary:
+This insight analyzes the performance impact of resources loaded from third-party servers and aggregates the performance cost, in terms of download transfer sizes and total amount of time that third party scripts spent executing on the main thread.
+
+## Detailed analysis:
+The following list contains the largest transfer sizes by a 3rd party script:
+
+- imgix: 172 kB
+- Google Tag Manager: 163 kB
+- Google Analytics: 20.5 kB
+- web.app: 823 B
+
+The following list contains the largest amount spent by a 3rd party script on the main thread:
+
+- Google Tag Manager: 28.1 ms
+- Google Analytics: 5.8 ms
+- noondiphcddnnabmjcihcjfbhfklnnep: 1.7 ms
+- web.app: 0.2 ms
+
+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.
+
+## Estimated savings: none
+
+## External resources:
+- https://web.dev/articles/optimizing-content-efficiency-loading-third-party-javascript/
+=== end content