XPages: 2 very easy performance optimization tricks

Here are 2 very easy ways to optimize performance for your XPages applications:

  • Enable “Use runtime optimized JavaScript and CSS resources” to have your JS and CSS files combined into fewer files. This reduces the number of HTTP requests that the browser has to make against your server and application and thereby makes the site load much faster.
  • Select “GZip” as the compression method to have your Domino server compress files and images. This reduces the amount of data that the browser has to retrieve from your server and application which again makes your application load much faster

Both of these settings are in Application Properties on the XPages tab.

Once you have done those two, you now have more time to go into detailed performance optimization and look at optimizing backend code, server settings, and much more. Tim Tripcony has answered a question in the XPages Development forum about performance optimization that has a lot of details about performance optimization.

6 thoughts on “XPages: 2 very easy performance optimization tricks

  1. Hi Per,

    your tips are valuable and true for production environments and pre release testing. However I wouldn’t recommend to activate the compression settings during the development phase since changes in css and javascript resources do not make it to the application as you would expect. You always have to clean your browser’s cache and rebuild a couple of times before you see your changes which can be very frustrating. So as soon as you are done with development and testing activate the compression settings and be happy with the faster loading site 😉

  2. I have tried to use the runtime optimized CSS and JS but it rendered my CSS useless. I think it might be because one of my CSS is a Page object and not a StyleSheet object. I did that to compute a few image locations since it is a CMS tool.

  3. Pingback: XPage settings | XPages.dk

  4. Hi Per

    I noticed that an application I’m building lost the classes in the “second” stylesheet loaded when having checked “Use runtime optimized Javascript and CSS resources” (think it’s enabled by default). Had to uncheck…
    And I am using only stylesheet objects…

    Sad of course since I wan’t as good performance as possible. 🙂

    Ove

Comments are closed.