Spike: Football scores header caching

The purpose of this ticket is to investigate whether we can do more caching in the webview to reduce client-initiated requests for the header / scores and tabs and to ascertain how this benefits slower mobile connections on web as well as behaviour in the iOS and Android app, which is currently where we are seeing the poorest performance.

In particular, once the scores header has loaded and rendered, it may not need to be re-rendered every time the user navigates to a new tab and the view changes.

Please look at:
- Whether this can be cached in a meaningful way rather than loaded on request every time
- Limitations and risks, especially around cache invalidation during live matches to ensure live content doesn't go stale
- Whether there are approaches that could help on both iOS and Android in particular, or if there might be other options we should explore than caching to improve performance