Page Performance Guide

This guide will help you troubleshoot performance issues in your Nintex Apps pages.

Understanding Page performance bottlenecks

Page performance issues usually appear in one of four areas. Check the following:

• Network latency: This is the time it takes for data processed in Nintex Apps in Apex to make its way through the internet to your web browser. On modern web browsers with fast internet connections, this is rarely an issue. However, it is good to at least measure this and eliminate it as a possible issue.

• Client-side processing and rendering: Once data from Salesforce makes its way to your web browser, the Nintex Apps Javascript code kicks in and starts rendering the components on your page. Modern web browsers will usually perform this task very quickly, but this is a good aspect to measure as well.

Measure, Tweak, Measure

One of the most important concepts in optimizing any performance is to be careful not to micro-optimize. Micro-optimization is harmful when you sacrifice clarity for some small (or possibly nonexistent) performance gain. Performance tweaks are only useful when they produce faster performance, and we can only know this if we measure it. Modern web browsers include some amazing tools for figuring out exactly why and at what step of the process you Nintex Apps page is taking the most time. The general cycle that we'll follow is below.

• Measure : Use the tools mentioned in this document to check how long each step of your page takes. Since page load times can change, run the tests several times to get a good idea of the usual performance.

• Tweak: Once you know which areas take the most time, make one of the changes suggested in this document to improve those areas.

• Measure: To determine if your tweak actually made a difference, measure the performance of your page again.

Diagnosing client-side issues

After looking at your network tab of your Web Browser's developer console, you've determined that Client Side performance is your problem, follow the tips below.

• Use a modern web browser: Self updating, modern browsers like Chrome, Safari, Firefox or Microsoft Edge are the best way to experience Nintex Apps. These browsers are sometimes 10 to 20 times faster than older browsers like Internet Explorer 8 or 9.

• Consolidate CSS and Javascript files to minimize HTTP requests: The more HTTP requests your page makes for resources, the slower it can be. However, be sure not to do these kind of optimizations unless your measurements show that it would help.

• Reduce the page size of your Table components: The more elements your browser has to render on page load, the slower it will be. Changing the Visible rows property on your tables from Show all to 10 could improve client side performance.

• Defer rendering of tab contents property on Tab Set components: Doing this will let your browser wait to render the contents of tabs until they are opened.

Tips for improving table filter and search performance

• Uncheck the Apply filters and Search immediately property on tables: Although this won't actually improve the performance of your queries, it could improve your users' experience. With this property unchecked, end users can set all of their filters exactly how they want them before executing a filter. When this box is checked, filters are executed immediately after a filter is changed.

• Follow the same principles outlined in the improving query performance section: When filtering a table, for the best performance, you'll need to adhere to the suggestions mentioned in the section above on Query Performance. If inefficient SOQL is generated by your filters, your response times will be slow.

• Specify individual search fields and operators: By default, table searches are executed on all searchable fields. This is great for small data sets, but for larger ones, this can cause searches to be slow. Nintex Apps allows you to specify exactly which fields are searched and which operators to use. Remember that contains operators are the slowest.

• Use SOSL to improve search performance: If you check the Use SOSL to improve search performance box, the table will use Salesforce's specialize search language to do your search. This will usually improve search performance. However there are some drawbacks including the inability to search data on parent records.

Diagnosing and improving Lookup Search performance

To investigate lookup search performance issues, follow the same diagnostic steps as in the Table Filter and Search Performance section. Except this time, type a search into a lookup search field. An apexremote line item will show up in your network console.

Tips to improve lookup search performance are the same as items 2, 3 and 4 of the Table Filter and Search Performance section.