Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Optimizing application load time

Updated on April 5, 2022

You run a preflight optimization to reduce an application’s unnecessary static content and improve its loading time.

Before you begin: Review your compliance score, and take corrective action to reduce static content in your application. For more information, see Improving your compliance score.
  1. In the header of Dev Studio, click ConfigureUser InterfaceApplication readinessPreflight optimization.
  2. On the Preflight Optimization screen, click Add optimization.
  3. In the Add optimization configuration dialog box, complete the following steps:
    1. In the Access group list on the Basic tab, select the access group that you want to optimize. The associated portal name is displayed on the right.
    2. Under Optimize, specify whether you want to optimize JavaScript files, Cascading Style Sheet (CSS) files, or both
    3. Optional: To reduce the size of your JavaScript files by removing comments and other unnecessary elements, select the Use JS Compacting check box.
    4. On the Advanced tab, you can select individual rules that will be included in—or excluded from—the analysis of the application's design-time model.
    5. Click Submit to save the optimization's configuration and start the analysis.

      If you are running the access group's preflight optimization for the first time, or if you selected the Use JS Compacting check box, the process might take a few minutes.

  4. Optional: To return the application to its previous JavaScript and CSS usage temporarily, clear the Enable check box on the Preflight Optimization screen to temporarily disable the optimization for the access group and portal).  

    You might do this if you encounter problems in the application and want to isolate them for testing and correction before you repeat the optimization process.

Result: After optimization, the application uses the optimized files by default.
What to do next:

View the report to see optimization details such as the difference between the original size and the optimized size of the static content.

If you change the portal, the application, or the application’s skin, repeat the preflight optimization process to remove any unnecessary static content introduced by your changes.

  • Rerunning a preflight optimization

    If you change the access group's portal, the application, or the application’s skin after running the preflight optimization process, repeat the preflight optimization to remove any unnecessary static content—or add necessary static content—introduced by your changes.

  • Checking results and JavaScript file dependencies

    View the preflight optimization report to see a list of components by category and to compare the static content’s original size to its optimized size.

  • Improve application loading time with preflight optimization

    Most of the static content for an application—the JavaScript files and Cascading Style Sheet (CSS) files—loads when the user starts the application. By using preflight optimization to reduce unnecessary static content, you can speed up your application’s initial display time, which can be especially important for applications that users access occasionally or just once.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us