Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Instance performance in Next Experience

View the performance-based information, including the UI loading times, for any recently accessed Next Experience page by using the client interaction table.

Key benefits

  • Monitor your instance performance and view this information for up to seven days.
  • Identify and investigate performance issues, such as slow UI load times.
  • View the server response times.

The following table lists the performance data that you can view in the client interaction table. You can find this table by navigating to All > System Logs > Client Interactions.

Header itemsDescription
CreatedDate and time that the interaction was recorded.
Total UI TimeTotal time, in milliseconds, from when a user initiates an interaction, such as loading or navigating, until the UI is idle. Includes rendering and network request time, and may be affected by user interruptions.
Content Download TimeTotal time, in milliseconds, spent downloading resources from the server during the interaction.
UXF Screen RouteRoute that is used to load the page for the given experience. For example, if the page is accessed from a list or form, Classic is displayed. For a workspace, the route defined in UI Builder is displayed.
ReferrerURL that initiated the interaction.
ApplicationApplication associated with the accessed URL.
TypeInteraction that is being measured. Type options include: - `PAGE_LOAD`: A full page load. - `NAVIGATION`: Routing within a single page application. - `IN-PAGE`: Time taken for interactions within the page, captured for limited interaction types.
InterruptionType of page load interruption and information about the type of interruption. If there was no interruption, the record displays none. The page load interruptions can impact the total UI time metric.
NameContextual label for in-page interactions.
DataAdditional contextual details for in-page interactions.

UI timing metrics

  • total_ui_time: includes network request time and rendering time.
  • fci_time (First Component Interactable): time when the user first interacts with the UI.
  • ui_time_before_load and ui_time_after_load: time before and after the application shell finishes loading. These values are not always populated.

Network and download metrics

  • network_latency: approximate network round-trip time using a cached static resource. Useful for comparing performance across regions.
  • content_download_time: total time spent downloading resources during the interaction.
  • client_cache_hit_rate: percentage of requests served from the browser cache.

Server and transaction metrics

  • total_response_time: total response time across all related transactions.
  • total_sql_time and total_sql_count: total time and number of SQL operations.
  • total_business_rule_time and count: time and count of business rule execution.
  • total_txp_time: time spent actively processing transactions, excluding wait times.

UX routing details

  • ux_screen_route: the route used to load the screen in Next Experience.
  • ux_screen_fields and ux_screen_params: required and optional parameters used to load the screen.

Additional data

  • linked_txc_metrics: JSON payload containing detailed client-side transaction metrics.
  • page_variant_sys_id: identifies the specific screen variant displayed to the user.

  • View the server response time
    View the server response times that are associated with your Next Experience instance by using the client interaction table.

Parent Topic:Configuring the Next Experience UI