category
Performance & Timing
Long Animation Frames, Event Timing, Soft Navigation, render-blocking, freeze, CPU performance, bimodal timings.
16 of 17 demos built, across 11 releases.
Chrome 152 (1)
-
CPU Performance API
Starting in Chrome 152, Chrome introduces the CPU Performance API, which allows web applications to determine the CPU performance of a user's device. This API targets web applications that will use this information to pr...
Chrome 151 (2)
-
Declarative Performance Observer
The Declarative Performance Observer proposes a reliable browser-resident telemetry system that reports of performance metrics from navigation initiation to page termination. By using a declarative HTTP response header, ...
-
PerformanceSoftNavigation and InteractionContentfulPaint performance entry
Adds "soft-navigation" and "interaction-contentful-paint" PerformanceEntry types to the web performance timeline to track interaction-driven page performance, including for "soft" navigations (JS-driven navigations in Si...
Chrome 148 (3)
-
Container Timing
The Container Timing API enables monitoring when annotated sections of the DOM are displayed on screen and have finished their initial paint. A developer will have the ability to mark subsections of the DOM with the cont...
-
Content type in Resource Timing
Adds the contentType field to PerformanceResourceTiming to hold a string corresponding to the content type of the fetched resource as returned by the server.
-
Long Animation Frames style duration
Add `styleDuration` and `forcedStyleDuration` information to the Long Animation Frame API, enabling developers to distinguish style and layout times.
Chrome 146 (1)
-
CPU Performance API
Starting in Chrome 152, Chrome introduces the CPU Performance API, which allows web applications to determine the CPU performance of a user's device. This API targets web applications that will use this information to pr...
Chrome 145 (2)
-
Container Timing
The Container Timing API enables monitoring when annotated sections of the DOM are displayed on screen and have finished their initial paint. A developer will have the ability to mark subsections of the DOM with the cont...
-
Enabling Web Applications to understand bimodal performance timings
Web applications may suffer from bimodal distribution in page load performance due to factors outside of the application’s control. For example, when a user agent first launches in a "cold start" scenario, it must perfor...
Chrome 144 (1)
-
Performance + Event Timing: InteractionCount
The Event Timing API is part of the Performance Timeline and is used to measure the performance of user interactions. Certain Events will have an interactionId value assigned to them, and this is useful for grouping rel...
Chrome 139 (3)
-
Full frame rate render blocking attribute
We propose to add a new render blocking token full-frame-rate to the blocking attributes. When the renderer is blocked with the full-frame-rate token, the renderer will work at a lower frame rate so as to reserve more re...
-
PerformanceSoftNavigation and InteractionContentfulPaint performance entry
Adds "soft-navigation" and "interaction-contentful-paint" PerformanceEntry types to the web performance timeline to track interaction-driven page performance, including for "soft" navigations (JS-driven navigations in Si...
-
Scroll Anchoring Priority Candidate Fix
Currently, scroll anchoring algorithm selects priority candidates when they are available as anchor targets. The priority candidates are currently a focused editable element and find-in-page highlights. This can caus...
Chrome 136 (1)
-
Enabling Web Applications to understand bimodal performance timings
Web applications may suffer from bimodal distribution in page load performance due to factors outside of the application’s control. For example, when a user agent first launches in a "cold start" scenario, it must perfor...
Chrome 135 (1)
-
Enabling Web Applications to understand bimodal performance timings
Web applications may suffer from bimodal distribution in page load performance due to factors outside of the application’s control. For example, when a user agent first launches in a "cold start" scenario, it must perfor...
Chrome 133 (1)
-
Resource timing: revert responseStart change and introduce firstResponseHeadersStart
Resource timing: - responseStart returns the first response, either early hints (interim) or final - Expose the final response headers (2xx/4xx/5xx) time as finalResponseHeadersStart.
Chrome 132 (1)
-
Resource timing: revert responseStart change and introduce firstResponseHeadersStart
Resource timing: - responseStart returns the first response, either early hints (interim) or final - Expose the final response headers (2xx/4xx/5xx) time as finalResponseHeadersStart.