> Because no one knows how to build a sensible web service any more, the page loads a 1.3MB JSON file containing every number that Barclays has. While other co

> Because no one knows how to build a sensible web service any more, the page loads a 1.3MB JSON file containing every number that Barclays has. While other comments have already mentioned that it's actually "only" ~190kB which get transferred thanks to gzip compression, there is still a lot of potential for a smaller transfer size by simply using brotli instead of gzip for compression. With brotli the size of this file is <60KB, so only less than a third of the file size of the gzipped data. Using brotli would be an easy win and improve performance of loading all other assets as well, without the need to change anything in the actual implementation of the website, however Barclays Bank is probably still running a webserver stack which doesn't support brotli yet.