Lightning Page Performance
Several factors can negatively affect your Lightning page’s performance at runtime. For example, your users can run into page performance issues if they aren’t using the latest version of a Salesforce recommended browser to view the page. Some factors you can control, and others you can’t. Here are some ways you can improve performance while configuring your page in the Lightning App Builder.
Required Editions
| Lightning App Builder available in: both Salesforce Classic and Lightning Experience |
| Lightning Home and utility bar pages available in: Lightning Experience |
| Lightning app and record pages available in: both the Salesforce mobile app and Lightning Experience |
| Email application pane pages available in: both Salesforce Classic and Lightning Experience |
Available in: Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
Consider the number, type, and placement of components on the page. These design-related issues can cause a page to load slowly:
- Too many components visible on page load
- Too many heavy-impact related lists visible, especially those lists with multiple-object relationships
- Too many fields in your Record Detail component
- Having the News or Twitter component visible
If your page falls into one or more of these categories, we recommend that you move some components into a non-default tab or Accordion component section, unless you’re designing the page for blind or low-vision users. For the heavy-impact related lists, we recommend that you move the related lists lower on their respective page layouts so that they aren’t part of the initial page load.
If your Record Detail component has many fields, we recommend that you reduce the fields on your page layout to fewer than 60. Alternatively, move the Record Detail component into a non-default tab or Accordion section so that it’s not part of the initial page load.
For pages that are viewed on a phone, we recommend a maximum of eight visible components per page. If a page has more than eight, put some in a tab or Accordion section or hide them for mobile with a visibility filter.
You can see how your pages are performing in the Lightning Usage App from the App Launcher. It shows you the most used pages in your org and their page load time by browser or by page.
Performance Analysis for App Builder automatically runs when you build a page. If your page performance is poor or moderate, recommendations to improve performance appear. You can manually check a Lightning record page’s runtime performance at any time by clicking Analyze from the Lightning App Builder toolbar. It assesses page performance based on all visible standard and custom components on the page. Components in nondefault tabs and Accordion sections aren’t analyzed.
The User Metrics card provides 90 days of your org’s user data such as browser speeds, network latency, and number of cores. Use this information to help you decide which Performance Analysis for App Builder recommendations to take.
Considerations
- If a page has more than 5 related lists or more than 25 fields in the record detail, users can encounter performance issues when viewing the page in the Salesforce mobile app.
- In the Performance Analysis for App Builder tool:
- Components that are restricted to the desktop form factor via a visibility rule aren’t included in the phone form factor performance assessment.
- Analysis of page performance on a phone is available only on pages whose template supports the phone form factor.
- Components aren't the only factors influencing page load time, so the numbers in the component impact chart don't add up to 100% of the predicted page load time.
- Analysis of pages for the desktop form factor is measured in seconds. For the phone form factor, the page is scored based on the components that are visible when the page loads on a phone.
- User metrics are org-specific or page-specific data. Previously activated pages display metrics from visits to that page. New pages display metrics from visits to all org pages. Metrics displayed in a sandbox can differ from metrics in production.
