Implement the lazy-loading approach in Technician RBA to improve performance

In the Technician RBA application from MAS 9.0.3 when we open "New work order (via Quick Reporting)" screen via the plus button, the loading of the screen takes too much time. 

We have analyzed the network requests being triggered when that screen is loading. There are two specific HTTP GET requests to Manage API that take most of the time:
1. maximo/oslc/os/mxapiasset - loading first 100 assets, this request takes 2-7 seconds.
2. maximo/oslc/os/mxapioperloc - loading first 100 locations, this request takes 3-8 seconds.

We noticed that the first screen load is terribly slow (20 seconds to load the screen where requests to mxapiasset and mxapioperloc take 7 and 8 seconds accordingly). But the subsequent screen loads are also still very slow (7-10 seconds to load the screen where requests to mxapiasset and mxapioperloc take at least 2 and 3 seconds accordingly). This is a screen that should not require much data, it's a template screen for entering new work order details, so preferably it should load instantly.

I'm specifically interested in getting it to work faster in RBA, i.e. what you get in your browser by opening "<maximo_host>/maximo/oslc/graphite/techmobile/index.html". There is a concept of preloaded database for Maximo Mobile that can improve the performance but it's only applicable to the native Maximo Mobile application and it's not supported by the in-browser RBA.

I understand that some caching approach is implemented in RBA but I've got some ideas how it can be improved:

• Lazy-loading approach should allow loading the data only when it's actually needed and without blocking pages. Initializing the cache can be performed on screens where data is actually required instead of loading it on the template screen that should load instantly.
• The preemptive data loading is actually a good idea for even better performance, however it should be done asynchronously in the background without blocking the screen where that data is not needed.

Please also see the attachments (logs and screenshots) in the linked support case.