Measure Lightning Experience Performance and Experienced Page Time (EPT)

-

Lightning Experience Performance and Experienced Page Time 

Lightning Experience Performance: Lightning Experience is the modern, user-friendly interface provided by Salesforce. "Lightning Experience Performance" refers to the overall speed and responsiveness of the Lightning Experience interface. This includes how quickly pages load, how fast data is retrieved from the server, and how smoothly users can navigate through different features and functionalities within the interface.

Experienced Page Time: This metric specifically measures the time it takes for a user to interact with a page in the Lightning Experience interface. It includes the time it takes for the page to load initially, as well as any subsequent interactions the user performs on that page, such as clicking buttons, entering data into fields, or navigating to different sections of the page. Experienced Page Time provides a more detailed insight into the user's actual experience while using the interface, beyond just the initial page load time.

Salesforce offers four ways to measure EPT.

Lightning Experience: Add an EPT counter to Lightning Experience.

Lightning Usage App: View aggregated page and browser performance.

Custom Reports: Build custom reports using Lightning Usage App objects.

Event Monitoring: Use event types to monitor performance.

Add an EPT Counter to Lightning Experience

Adding eptVisible=1 will add the page load time counter to your Lightning Experience header, but won’t display the network bandwidth. Unlike enabling Lightning Component Debug Mode, the component code is minified and will have less impact on performance time.

When using Lightning in Salesforce, Experienced Page Time (EPT) is a performance metric that measures how long a page can load and be ready for user interaction.

To display the page load time/EPT counter on a page, simply add ?eptVisible=1 at the end of the URL. For example, https://domain.lightning.force.com/lightning/page/home?eptVisible=1.









Enabling Lightning Component Debug Mode

Enable Lightning Component Debug Mode adds a counter to the Lightning Experience header that shows page load time and network bandwidth.

Remember, performance may be impacted when enabling this setting because the component code won't be minified, and caching will be disabled.
















Use the Lightning Usage App to Measure EPT

The Lightning Usage App is a great way to track the adoption and usage of Lightning Experience. To open it, click the App Launcher and search for Lightning Usage.

Example

Slowest Desktop Record Pages, Most Viewed Pages, Single Page Performance and Slowest Desktop Record Pages


Lightning Usage App to see how browser performance affects EPT




























Build Custom Reports Using Lightning Usage App Objects

For more detailed analysis of your page's performance, you can use Lightning Usage App objects to create customized reports.


















Monitor Performance with Event Monitoring

Use the Lightning Page View event type to measure page performance in Event Monitoring. The Lightning Page View event type tracks information such as the page a user visited, the browser they used, how long the user spent on the page, and the load time for the page.

In the example below, you can see metrics for when a user accessed the page (“pageStartTime”), how long they spent on the page (“duration”), and the Experienced Page Time (“EPT”).

















References

Comments

Post a Comment

Popular posts from this blog

Introduction to Salesforce Agent Script: Build Predictable AI Agents

-
Image
Please visit here for more details - https://ayaninsights.com/guestblogs/introduction-to-agent-script/ In my latest blog, I introduce Salesforce Agent Script and explain how it helps teams build AI agents that are more predictable, controlled, and aligned with business processes. Large language models are flexible, but relying only on natural-language instructions can sometimes produce inconsistent results. Agent Script addresses this challenge by combining the conversational capabilities of an LLM with structured business logic. The blog explains how developers can use conditions, variables, actions, topics, and transitions to control how an Agentforce agent behaves. Agent Script supports familiar logic such as if/else conditions, value comparisons, sequential actions, and checks for missing data. I also cover its core structure, including system settings, configuration, global variables, languages, connections, and topic blocks. The start_agent topic acts as the entry point for each...
Read more

Anti-Patterns in Salesforce Agentforce: What to Avoid When Building AI Agents

-
Image
Salesforce Agentforce is powerful because it allows teams to build AI agents that can understand user intent, retrieve grounded information, execute actions, and support business workflows across Salesforce. But like any powerful platform, the quality of the implementation matters. A good Agentforce implementation does not start with “How many things can the agent do?" It starts with “What problem should the agent solve reliably?” That is where anti-patterns come in. Anti-patterns are common implementation habits that look useful at first but eventually create confusion, poor user experience, inconsistent answers, or hard-to-maintain agents. Below are some of the most common Agentforce anti-patterns and how to avoid them. 1. Trying to Build One Agent That Does Everything One of the biggest mistakes is designing a single agent to handle every business process, every department, and every possible customer question. At first, this feels efficient. One agent, many use cases. Bu...
Read more

MCP vs. Traditional APIs: Choosing the Right Integration Approach

-
Image
Enterprise integration has traditionally been built around APIs. Applications send structured requests, services process them, and predictable responses are returned. This model has supported everything from payment processing and customer portals to mobile applications and large-scale system integrations. The rise of AI agents introduces a different integration challenge. An AI agent does not always follow a fixed sequence designed in advance. It may need to determine which system to use, discover the operations available to it, gather relevant context, and select the appropriate action based on a user’s request. This is where the Model Context Protocol, or MCP, becomes relevant. MCP and traditional APIs are related, but they solve different problems. APIs expose system capabilities. MCP provides a standardized way for AI applications to discover and use those capabilities as tools and contextual resources. Understanding this distinction is important when designing enterprise AI solut...
Read more