You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is only and intermediate solution regarding caching.
Ideally only index.html should be exposed to this caching technique, the rest of the assets (JS, CSS, IMG, ...) would be handled with:
However, the last one can be applied only if the generated JS files have a suffix that changes on build or on checksum.
The previous configuration are just workarounds and do not help for the first render where people is blocked.
For that, a mechanism to optimise the loading or reduce the size of the payload is needed.
Tested on ocis.owncloud.com with network throttling as depicted in the video:
web-performance.mov
To alleviate renders after initial page load we have the following directives in NGINX:
This is only and intermediate solution regarding caching.
Ideally only
index.htmlshould be exposed to this caching technique, the rest of the assets (JS, CSS, IMG, ...) would be handled with:However, the last one can be applied only if the generated JS files have a suffix that changes on build or on checksum.
The previous configuration are just workarounds and do not help for the first render where people is blocked.
For that, a mechanism to optimise the loading or reduce the size of the payload is needed.