look into using fetch priority

priority (high | low | auto) can now be set for fetch requests in Chrome 101. We should look into whether we improve load times by using this to prioritize resources. We already try to prioritize requests by making them in order of priority, so it isn't clear if this will be very useful at this point.

Completed Origin Trials
The following feature, previously in a Chrome origin trial, is now enabled by default.

Priority Hints
Priority Hints provides a way to indicate a resource's relative importance to the browser, allowing more control over the order resources are loaded.

https://blog.chromium.org/2022/03/chrome-101-federated-credential.html

A USVString indicating the hinted priority of the request. > Possible values are:

high: Fetch the request at a high priority relative to other requests of a similar type.
low: Fetch the request at a low priority relative to other requests of a similar type.
auto: Default mode, which indicates no preference for the fetch priority. The browser decides what is best for the user.

https://developer.mozilla.org/en-US/docs/Web/API/Request/priority

Start by reviewing the existing request-order prioritization described in the issue and the Fetch API's Request.priority values. Measure whether applying high, low, or auto changes load times for relevant resources; done requires documented evidence and a clear decision on whether implementation is warranted.