Performance

Preloading static content

One way to improve the load time performance of Office for the web applications is to preload Office for the web’s static content (JavaScript, CSS, and images) into the user’s browser cache. This will help ensure that when the user opens a document in Office for the web, they can use the previously cached static content and do not need to download that data when they first try to load Office for the web.

To support preloading static content, Office for the web provides two WOPI actions for each Office for the web application in its discovery XML, one to preload static content for the view action (preloadview), and a second to preload static content for the edit action (preloadedit).

Hosts can use these URLs just like they use other Action URLs, by pointing iframes in their pages at the action URL. Unlike most action URLs, the WopiSrc and access token do not need to be specified in order to use these actions.

Hosts can include both preloadview and preloadedit in their pages to preload static content for both. Note that the static content preload actions contain the UI_LLCC placeholder value, which should be replaced with an appropriate language for the user so that the proper localized static content is preloaded.

Tip

If you wish to preload static content for all applications and both view and edit modes, you must load multiple actions, one for each application/mode combination.

🔧 Optimizing document viewing for high volume

Attention

Sorry, this documentation hasn’t been written yet. You can track the status of issue #5 through our public GitHub issue tracker.