We currently inline the portal JS, meaning that browsers that don't have JS support still have to load it, even if they're on shoddy connections. We can do better. Let's deprecate the inlining and store it as a separate, distinctly requested file. As a side-effect we will be able to measure the level of JS support our users have.
We'll need to:
- create the distinctly request-able JS file
- update the portal page to use the request-able JS file
- push to production
We'll need this information sooner rather than later - and we'll need to base our A/B testing on these results.