< Back to Insight

How to Make Your Salesforce Instance Performance Gold Medal Worthy

The Tokyo Summer Olympic Games may have come to a close, but it’s not too late to focus on making sure your Salesforce instance’s performance is gold medal worthy. After all, poor performance can have a negative ripple effect across your entire business. It can be distracting to your users, hinder productivity, lower confidence in usage and adoption, and result in an overall poor user experience.

Learn how to get on the path to gold medal success and ensure your Salesforce instance performs at an elite level.

Where to Start

The hardest part is often figuring out where to start. Ensure a smooth start by:

  • Drawing a system diagram to visualize current and future features, systems, and users that involve Salesforce. For each part of the system, estimate peak load levels, average load levels, and feature use. Consider user arrival rates, login rates, and pages.
  • Estimating the size and shape of your data, including the number of accounts, users, feeds, groups, and other objects.
  • Understanding data hierarchies and the related data sets which get loaded when viewing individual records.

Measure Performance

The next step is to measure your Salesforce instance’s performance to help gauge and prioritize areas for improvement. Keep in mind:

  • Salesforce provides standard tools such as Lightning Usage App, which allows you to view and measure page and browser performance. It gives you a summary view of what your users are experiencing. It’s a great tool to get started on understanding the performance of your Salesforce instance.
  • The Lightning Usage App is built around data on the Lightning Usage App objects. If the standard dashboards and reports do not give you the level of data you require or require more than the standard reports and dashboards, you can build custom reports and dashboards using Lightning Usage App objects.
  • Salesforce also offers additional tools such as Events Monitoring Analytics as part of the Salesforce Shield package. The Event Monitoring Analytics app makes it easy to base your actions on insights drawn from data pulled from Salesforce event logs. These event logs can be configured to monitor a variety of actions that the users perform in Salesforce, giving you insights into the usage and performance of your system.
  • Running Salesforce Optimizer to get recommendations for feature improvement, clean up customizations, reduce complexity, and drive feature adoption.

Improve Performance

Now that you’re measuring your performance, it’s time to look at how to make improvements to give your users the experience they deserve to be productive.

Reduce Technical Debt

  • Certain design decisions taken based on the capabilities of the platform may be appropriate when the platform was implemented. But over the lifetime of the application, these design decisions become obsolete because of the advancements in the product and platform capabilities. Revisiting the design decisions regularly and frequently ensures that there is minimal technical debt accumulated over time. Examples include a large number of unused fields or using now obsolete automation tools, such as Workflows. Technical debt could also be a result of old workarounds that were required at one time, but that Salesforce has since patched or provided a direct solution for the previous workaround.

Improve Page Design

  • 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 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.

Understand Custom Lightning Components

  • Optimize server round trips for data retrieval. Before making a call to the server, make sure there’s no other option to obtain the data. If the data needs to be retrieved, make sure only the essential data is called.
  • Lazy load occasionally accessed data. Don’t preload data that the user may never ask for.
  • Use caching techniques for fewer server call-outs.
  • Consider using composite requests by combining several individual requests into one.
  • Showing every available piece of data and every available tool on the screen just in case the user may need it is generally not considered a good UI practice. It can also significantly impact the performance of your application. Today’s interactive design guidelines favor progressive disclosure.
  • Use third-party libraries sparingly. Many of the utilities that required third-party libraries are now available standard in the languages.

Examine Long-Running Processes

  • One of the most common problems that pop up out of the blue is the “Apex CPU timeout error.” While the keyword pex may have you believing it’s a code issue, it’s usually caused by recursive and long-running automation processes. Consider optimizing these processes by implementing various design patterns.

Optimize Images

  • Use web-optimized images rather than full resolution.

Employ Device and Browser Best Practices

  • Ensure that your users are using the latest supported versions of the browsers and devices. Outdated browsers and devices can have a significant impact on the performance of the application.

Consider Console Navigation

  • Console navigation is a tab-based workspace that can perform faster for certain user flows, particularly in multitasking.

To learn more about improving your Salesforce performance, contact us today.