The InitContainerEntry
interface documents key moments related for the container preparation work before the Lynx page is displayed. It inherits from PerformanceEntry
.
In the initialization process, the metrics are defined as shown in the figure below:
The key moments provided by this entry rely on the container through LynxView.setExtraTiming
provision.
This example demonstrates how to retrieve InitContainerEntry
。
Returns the entry type, which is always init
.
Returns the entry name, which is always container
.
The time when the container starts loading a Lynx page。This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.
The time when the container initialization starts. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.
The time when the container initialization completes. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.
The time when the container starts preparing the TemplateBundle. "Preparing" means obtaining the TemplateBundle via network download, loading local cache, or any other method. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.
The time when the container finishes preparing the TemplateBundle. "Preparing" means obtaining the TemplateBundle via network download, loading local cache, or any other method. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.
LCD tables only load in the browser