Org Configuration Best Practices

Unoptimized Visualforce implementations can impact performance on Visualforce pages. Follow Visualforce best practices outlined in this developer guide.

Some orgs have Lightning Component debug mode enabled for certain users. Lightning Component debug mode negatively affects performance. Enable debug mode only for users actively debugging Lightning components.

Pages with many fields, inefficient custom components, or complex page configurations, can have long load times. To improve performance, consider simplifying those pages. Try these tips to get started:

• To get recommendations for feature improvement, clean up customizations, reduce complexity, and drive feature adoption, try running Salesforce Optimizer first.
• Use profiles to streamline the number of fields. Configure the page so that only the most relevant fields initially display for the user.
• Break page elements like fields, related lists, and custom components into different tabs. Display the most relevant information on the first tab, and move other information to other tabs. Components outside of the primary tab are rendered on demand, not in the initial page load.
• Move the Details component to a secondary tab, or reduce the number of fields displayed.
• Move the Related Lists component to a secondary tab, or use the Related List (singular) component instead. Try to keep the number of related lists to three or fewer.
• Test and refactor any inefficient custom components. See if you can replace any custom components with Lightning Actions. If you have to use custom components, follow the Lightning component best practices outlined in this developer blog.
• Consider using console navigation. Console navigation is a tab-based workspace that can perform faster for certain user flows, particularly in multitasking.