Tatoeba slowing down computers

[RyckRichards]

Reported by Hybrid on the Wall

Tatoeba slowing down my computer?

Maybe it's just a problem with my computer, but I've noticed that some parts of Tatoeba really slow down my computer now. The Wall is fine, but all the webpages that have lists of sentences, like the log or when I click "show more..." slow down my browser. Does anyone else have this problem or is it just my computer?

https://tatoeba.org/eng/wall/show_message/25792#message_25792

It happens to me when I use Firefox on Windows. Chrome is a little bit faster.

https://tatoeba.org/eng/wall/show_message/25804#message_25804

https://tatoeba.org/eng/contributions/latest
https://tatoeba.org/eng/contrib...of_user/Hybrid

If I try to scroll down, it's very slow and Firefox can even stop working for a while. This didn't happen before.

[ckjpn]

Is it tatoeba.org slowing down his computer, or the fact that tatoeba.org is sometimes slow?

My guess is this that it's the latter, and that this is likely not really a bug.

[RyckRichards]

By Pfirsichbaeumchen on the Wall

I have experienced the same problem, and I also use Firefox. Reducing the number of displayed sentences seems to help.

[ckjpn]

The way Pfirsichbaeumchen describes the problem and her solution implies this isn't a bug and that this issue can likely be closed.

[trang]

I'm closing this. It is not something we can do much about. Hybrid mentioned himself:

Thank you everyone for your answers. I think that it must be something with my computer.

[ghost]

I'm just passing by to let you guys know that I was able to duplicate this on my computer. And yes, it is a bug!

This is happening when users open this page.

I think the problem is that too many sentences are being loaded on the page.

How to duplicate the problem:

1. Log into your account;
2. Go to your profile page;
3. Click this link:

Edit:

• It isn't happening on chrome.
• It only happens when you load more than 10 sentences per page.

[jiru]

I set 100 sentences per page, yet I’m unable to reproduce the problem with your link.

[ckjpn]

http://www.webpagetest.org/

Perhaps the results stay online for a while.
Test for https://tatoeba.org/eng/activities/translate_sentences_of/bill

Firefox Test
http://www.webpagetest.org/result/160313_XS_7QW/

Chrome Test
http://www.webpagetest.org/result/160313_RB_7P0/

[ckjpn]

Google PageSpeed Insights for the same page.

https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Ftatoeba.org%2Feng%2Factivities%2Ftranslate_sentences_of%2Fbill

Mobile Screenshot taken from the results page.

[ghost]

@ckjpn Actually, you need to access this page:

https://tatoeba.org/eng/activities/translate_sentences_of/CK

• Using Firefox 45.0
• Set 100 sentences per page.

Edit: This is only happening on Tatoeba. I access a handful of sites with infinite scroll and the pages are loading smoothly.

[jiru]

@ckjpn Your are testing the time it takes to load the page. It has very little to do with the original problem, that is to say slowdowns while scrolling after the page is loaded.

[ckjpn]

I was just eliminating possibilities.

[ghost]

Reported by alexmarcelo on the Wall:

After the update, Tatoeba is so slow in my computer that I can't use it anymore. In Firefox, the interface looks OK, but I can barely scroll down and up. In Edge, the icons look weird and the buttons are not functional at all.

[ckjpn]

Could this possibly be caused by a CSS change done during the last update?

Perhaps if might be a good idea to revert back to what was being used before the update, until this can be figured out. Or, maybe use that blue announcement feature to suggest that visitors try using a browser other than Firefox.

[ghost]

Could this possibly be caused by a CSS change done during the last update?

Probably, but I'm not sure yet.

Or, maybe use that blue announcement feature to suggest that visitors try using a browser other than Firefox.

This is just bad UX. We must never suggest this to our users.

[ckjpn]

This is just bad UX.

I agree. What I meant was that temporarily this could be used if it's too much trouble to revert to the pre-update version of any feature that had CSS changed, assuming it's a CSS problem.