-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Researching/Discussing web UI speed optimization/tweaks #3790
Comments
Also related: #3385 |
Dealing with enabling compression – special for nginx and nextcloud documentation but maybe worth noting here: nextcloud/documentation#325 |
I've updated the post to reflect the comments so far. |
I added checkboxes to the ongoing items and added some more of them. 😉 |
Hi, To complement my message on the other post I would like to suggest that some sort of HTTP2 server push is implemented on the server side. This will allow HTTP2 enabled servers to push assets to the browser even before it fully computes Also, it should be quite simple to implement. In the case of the NextCloudPi web interface (quite a simple example), it amounts to one line
, and the result on a very slow QEMU ARM instance ( gray ball means pushed ) There's some informative links at the bottom of the blog post. Should I open a new issue for this "feature request"? |
I suppose this issue is still valid? If not, please close this issue! |
All of the items in the original issue have been addressed. And numerous unmentioned follow-up PRs have been merged. Closing this issue for the following reasons:
TLDR: This issue has served its useful life. Closing. :) |
By curiosity I checked my nextcloud instance on Google PageSpeed Insights and was a bit sad when I realized it didnt even score above 10/100 (actually got 2/100), Dropbox scores 52/100. Now I realize its hard to optimize a system like nextcloud since the data stored there should never be touched, or changed. However there are assets which could be tweaked, compressed and what not. At least thats what I think. So I want us to discuss what can be done and what cant be done here and plan a roadmap for delivering blazing fast UI.
Examples given by GPSI:
Ongoing:
Research
Goal
Beat dropbox's score of course and develop ideas for how to improve speed and responsivness on the web ui.
The text was updated successfully, but these errors were encountered: