I could start with this if noone else did.

Hi @AndersBillLinden
Thanks for the suggestion. The challenge is that, until we get the metric data, we do not know which websites will be displayed in the dashboard.
Example: Imagine you have 1,000 websites in Piwik. Only the 50 sites with most visits will be displayed by default in the dashboard. But when you first load the dashboard we do not know which 50 will be later displayed.

So I think it's not possible to make this change. Thoughts?

We can initially sort on site name instead of number of visits. The user can change the sort to the number of visits if he/she like. We can skip the pager and if the user clicks the column for number of visits, rows will rearrange as the user views the page. If the number of sites is low, I guess the current approach can be used.

We can always cache the order of the sites so that the initial sort order wll be the same as the one before. Then we can initially order by number of visits. We will visually indicate that a row is not yet updated.

We can initially sort on site name instead of number of visits.

we could not easily change the sort order here: it is important to sort on Visits by default to first display those most important websites.

@mattab What about my other suggestion?

I suggest that we order by visits initially and also cache that order. The next time a user wants to see the listing, it will come up and sequentially update/reorder (without using a pager).

@AndersBillLinden How long does it take on your Piwik to load the all websites dashboard? Ideally it should be very fast eg. under 1 second and we wouldn't really need to make this change.

Btw if you can upgrade to 2.14.0-beta the All Websites is a bit faster there already.

We can always cache the order of the sites so that the initial sort order wll be the same as the one before. Then we can initially order by number of visits. We will visually indicate that a row is not yet updated.

It sounds possible but I'm not sure that we need this added complexity in the dashboard... Our goal is to make the dashboard render very fast in most cases and ideally we don't need to be smarty with displaying the website data.

Btw if the All Websites is very slow, we should display a notification to explain to users why (and suggest them to setup Archiving cron): see #6210

I use the latest git version and I get a timeout displaying 154 sites. Maybe the number of sql queries is the real thief in this drama.

We can be sure there is a need, but maybe as you say the complexity of the dashboard should not be added to.

We have setup cron archiving and disabled browser archiving.
Still it takes a lot of time, seems like we are able to get a listing however.