Loading

Optimize Lightning Performance Checklist

Date de publication: Oct 13, 2022
Description

When users report that Lightning is slow there are a number of items admins and developers can review to improve Lightning performance. Lightning performance is impacted by three main areas: network performance, browser performance, and page complexity/customizations. In some cases, all three need to be investigated and improved to enable highly performant Lightning Applications.  

 

Résolution

Review Network, Browser, and Page Performance

   

Review Performance of a Lightning Page


Once you have identified a specific page that is causing performance issues review each in detail:
  • Validate the performance issue by measuring the EPT when loading the page
    • Use a URL suffixed with "?eptVisible=1" or “?0.aura.mode=PERFDEBUG“ to get more information about the page’s EPT. You can also enable Debug Mode for your user (note: this will cause additional slowness)
    • Test using different browsers/computers similar to what your end users have
    • Test using Chrome’s Guest or Incognito mode to eliminate any issues with browser extensions or plugins
  • Review the complexity of the page using App Builder: How many fields, related lists, VF pages, VF Components, standard and custom Lightning components have to load on the page? Does the user need access to everything when the page loads?
    • In App Builder Select Help > View Tips to see if there are any Tips specific to increasing performance or UI usability.
    • Break up the elements on a page using customizable tabs, everything but the primary tab will benefit from lazy loading to decrease EPT
    • If the Record Detail component includes a large number of fields move it to a separate tab and leverage the Related Record standard component (self-referential) to show a subset of fields on the primary tab.
    • If there are a large number of Related Lists move them to a separate tab and leverage the Related List - Single Component to show the most important Related List(s) on the primary tab or leverage Related List Quick Links Component
    • VF pages and VF Components should be moved to a separate tab whenever possible. Long-term VF pages can either be migrated to custom Flows, Standard Components, or Custom Lightning Web Components.
  • Quantify the impact of components on the page using a process of elimination - remove one element at a time from the page to determine if it is causing a performance issue
  • Leverage Chrome’s Developer Tools to take a Performance Profile Recording to analyze the page’s performance
Numéro d’article de la base de connaissances

000390330

 
Chargement
Salesforce Help | Article