Use HTML5's Application Cache Manifest file to help speed things up

[nolim1t]

Move the static files (maybe the whole load) to a HTML5 Application cache so there's less loading times (and less requests on the server). That way the whole site will only be fetched if the manifest file changes.

You can also use it to handle errors a lot more gracefully leading to a better user experience in general using the Application cache.

Happy to send a pull request if you guys don't want to really work on this.

[haustraliaer]

@nolim1t We definitely plan to do this, just have a lot of things to get through right now. Feel free to submit a PR if you'd like it to happen sooner - would be much appreciated!

I'm also curious as to how you see app cache handling errors more gracefully - could you elaborate on that?

[nolim1t]

@haustraliaer with the app cache you can listen for events such as whether the page can be loaded or not. Lets say the user can't get to the server you can show an offline page. But then again, if the app is all self contained , you can just display a warning note to say that some features may not work.

[haustraliaer]

Ah I see what you mean - sounds like it could work well. Certainly it's worth it for the caching alone. I'll see where we get to by the end of this month (current deadline for most of our issues) and consider looking at it then.

[ghost]

@nolim1t if you still feel like doing this, we'd certainly love a pull request.

@weilu Otherwise, is this something that could help us in the short term?

[weilu]

Our js bundle at the moment is 351 KB. The blockchain API request payload is much bigger in comparison. I'd say that this optimization is low priority.