Comment 2 for bug 1217532

Thank you for filing this. I debated what to do with it. For now, as written, this bug is invalid for the GUI. Everything is built in the browser in a single-page JS app, from a reasonably snappy API call that simply returns JSON.

More broadly, pre-rendered pages are one of many reasonable implementation strategies for different tasks. I doubt we'll be pursuing that in the short or medium term, at the least, and with other goals (authentication and various abilities associated with it) I'm not sure it is the right long term approach. Caches of content for anonymous users can still work quite well with this, or you can even pre-render parts of the page. That's an optimization discussion for well down the line, when things look different than they do now.

But most broadly, to Rick's point, the time it takes to load the GUI, and then for a browser to render a page, is something we can improve in a variety of ways, large and small. This is the underlying problem I think you are identifying. However, we need to identify a specific goal and a priority. I think that will be driven by ongoing conversation. I'm not confident that it is a true bug at the moment, or a low priority bug, or possibly a high priority one. I'll link you into related bugs as we make them.

Thanks again.