Slow Page Load Times in Nue (Salesforce Lightning)

The most common cause of slow Nue page loads is that the page is being opened through a legacy URL path that routes through an older, less optimized code layer (Aura) instead of the current Lightning Web Components (LWC). When this happens, an extra rendering layer is added on top of the optimized component, which causes the delay. This is especially noticeable in orgs with Lightning Web Security (LWS) enabled.

This typically happens when you reach a Nue page through:

If you are using the standard buttons provided by Nue on your Salesforce record pages (such as "Edit Line Items" on a Quote, "Manage Customer Lifecycle" on an Account, or the Lifecycle Manager tab), those already use the optimized path and should not cause this issue.

After the slow page finishes loading, look at the URL in your browser's address bar. This is the most reliable way to confirm whether the legacy path is the cause.

If the URL contains a component name that does not end in Container, you are on the legacy Aura path.

Example:

You may also see a yellow deprecation banner at the top of some Nue pages when loaded through the legacy path. However, this banner does not appear on every page or module, so the URL is the best way to confirm.

If you can confirm the URL contains a legacy component name (without Container), continue to Step 3 for the fix.

The simplest fix is to stop using the custom link or bookmark and instead navigate using the built-in quick action buttons that Nue provides on Salesforce record pages. These buttons always route to the optimized LWC path automatically.

Common actions and where to find them:

If any of these buttons are not visible on your record pages, a Salesforce admin can add them through Edit Page in Lightning App Builder. The quick actions are included in the Nue managed package.

If your org relies on a custom button, link, or formula field to open Nue pages, the URL needs to be updated so it references the newer LWC component name. The URL structure stays exactly the same. Only the component name changes.

The general pattern is:

For the full mapping of old-to-new component names and detailed URL examples, refer to the Aura Deprecation Upgrade Guide in our documentation.

If you need help identifying which buttons or links in your org need updating, contact Nue Support and we can assist.

If you've been reaching the page from a browser bookmark or a link saved in Slack, a wiki, or internal docs, delete the old link and re-save it after navigating through the correct path using one of the standard Nue buttons.

Will the old URLs stop working? Not immediately. The legacy Aura components are still included in the managed package for backward compatibility, but they add unnecessary load time and will be removed in a future release. We recommend updating as soon as possible.

Does this change affect my data or any functionality? No. This is purely about how the user interface loads. All features, data, and functionality are identical on both the old and new paths.

If you've confirmed that your pages are already loading through the optimized LWC path (URL contains Container, no legacy component names), and you're still experiencing slow load times, please contact Nue Support.

When reaching out, it's helpful to include:

This helps us investigate more quickly and determine if there's a different factor at play.