Slow Load of a Standard List Page

NetSuite provides list pages for bulk transaction processing such as Approve Sales Orders and Bill Payment.

If loading a standard list page is taking longer than usual:

1. Check the number of transactions displayed on the page.

• Transactions are listed in a sublist, with the fields required for the process.
• The value for each field is pulled from each transaction record before being displayed in the sublist.
• The time it takes to pull field values from a single record is multiplied by the number of transactions listed.

1. Check whether the list is customized.

• Click Customize.
• On the Additional Columns tab, review how many columns are selected.
• Additional columns affect performance; it is a best practice to only select the columns that are required.

1. Add filters to the list of transactions.

• Filters can positively impact performance by limiting the transactions listed.
• A best practice is to display only the transactions to be processed.

1. After the action has completed, review the Performance Details.
2. You can double-click the NetSuite logo in the upper left corner of any page in the NetSuite application to display Performance Details. This window is also known as the Page Email and Time (PET) window. For more information, see Identifying Performance Issues.

• If the largest portion of time is associated with the server, log a case with NetSuite Customer Support.
• If the largest portion of time is associated with the client:
• See Improving Client Performance and the SuiteAnswers article Client Side Performance Causes for tips.
• Determine whether the problem is related to the browser. See Adjusting Browser Settings.
• Determine whether a client script function is being triggered. See the following:
• Using the Scripted Records Page
• Client Event Types
• Client Script Best Practices
• If the largest portion of time is associated with the network:
• Perform a trace route going to system.netsuite.com. See Using a Trace Route to Troubleshoot Performance Issues.
• If possible, connect to a different network and observe whether the problem is still present. This step helps to isolate potential network factors.