v148 · Performance · demo
Content Section Timer
Three sections are annotated with containertiming. A PerformanceObserver catches each entry as the browser finishes painting that section.
Origin trial feature:
containertiming requires the Container Timing origin trial token in Chrome 148. This demo shows real API usage with a realistic simulation fallback.
containertiming="hero"
Hero Section
[ hero image loading… ]
containertiming="article"
Article Body
containertiming="sidebar"
Sidebar Widget
hero
waiting…
article
waiting…
Checking PerformanceObserver support…
// Mark sections in HTML:
// <section containertiming="hero">…</section>
// <article containertiming="article">…</article>
// Observe in JavaScript:
const observer = new PerformanceObserver(list => {
for (const entry of list.getEntries()) {
console.log(
entry.identifier, // "hero", "article", "sidebar"
entry.renderTime, // latest paint timestamp
entry.firstRenderTime,
entry.size // { width, height } of container
);
}
});
observer.observe({ type: 'container', buffered: true });
references
- Timing Dashboard — multi-element live dashboard
- Back to feature index
- ChromeStatus entry
- Container Timing API draft
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗