LargestContentfulPaint: renderTime property

Limited availability

This feature is not Baseline because it does not work in some of the most widely-used browsers.

The renderTime read-only property of the LargestContentfulPaint interface represents the time that the element was rendered to the screen.

Value

The renderTime property can have the following values:

  • A timestamp representing the time in milliseconds that the element was rendered to the screen.
  • 0 if the resource is a cross-origin request and no Timing-Allow-Origin HTTP response header is used.

Examples

Logging the renderTime of the largest contentful paint

This example uses a PerformanceObserver notifying of new largest-contentful-paint performance entries as they are recorded in the browser's performance timeline. The buffered option is used to access entries from before the observer creation.

js
const observer = new PerformanceObserver((list) => {
  const entries = list.getEntries();
  const lastEntry = entries[entries.length - 1]; // Use the latest LCP candidate
  console.log(lastEntry.renderTime);
});
observer.observe({ type: "largest-contentful-paint", buffered: true });

Cross-origin image render time

For security reasons, the value of the renderTime property was originally 0 if the resource is a cross-origin request. Instead the loadTime property should be used as a fallback.

Browsers may now expose a slightly coarsened render time in these situations. Check for browser support.

To expose more accurate cross-origin render-time information, the Timing-Allow-Origin HTTP response header needs to be set.

For example, to allow https://developer.mozilla.org to see an accurate renderTime, the cross-origin resource should send:

http
Timing-Allow-Origin: https://developer.mozilla.org

Alternatively, you can use startTime which returns the value of the entry's renderTime if it is not 0, and otherwise the value of this entry's loadTime. However, it is recommended to set the Timing-Allow-Origin header so that the metrics will be more accurate.

If you use startTime, you can flag any inaccuracies by checking if renderTime was used:

js
const isAccurateLCP = entry.renderTime ? true : false;

Specifications

Specification
Largest Contentful Paint
# dom-largestcontentfulpaint-rendertime

Browser compatibility

Report problems with this compatibility data on GitHub
desktopmobile
Chrome
Edge
Firefox
Opera
Safari
Chrome Android
Firefox for Android
Opera Android
Safari on iOS
Samsung Internet
WebView Android
WebView on iOS
renderTime
Cross-origin
Experimental

Legend

Tip: you can click/tap on a cell for more information.

Full support
Full support
In development. Supported in a pre-release version.
In development. Supported in a pre-release version.
No support
No support
Experimental. Expect behavior to change in the future.