Hi, I experienced some (for me serious delays) in the rendering performance. For example this thread in the syncthing forum: SSL Certs discovery v4 vs v6 - General - Syncthing Community Forum. I use the chrome on samsung s4. [图片] (screenshot of developer tools), rendertime ~11s, without js ~1s (at home over wlan) Thx in advance!

I can be wrong but on a early 2013 phone, with 1.5GHz processor this is bad but kinda expected? How is the timing loading meta.discourse.org and try.discourse.org ?

This phone has been 3years ago an high end phone. What is the phone distribution here on this site? Maybe there are less powerful phones. Mobile design is IMHO not only about the responsive layout. It is also about speed/bandwidth and hardware limitations on these devices. meta.discourse.org: http://www.webpagetest.org/result/160330_8K_592802ee00441a32192a5183af8ad1c9/ try.discourse.org: http://www.webpagetest.org/result/160330_49_024ca5619286ee2c338b3254e088d574/ forum.syncthing.org: http_://www.webpagetest.org/result/160330_YB_191aff8be451ac26636f4b115f2cc018/ You can see there is timerange with 100% cpu. P.S. forum.syncthing is the fastest

This tests are using the chrome emulation, and not real devices too. http://mobitest.akamai.com/m/results.cgi?testid=160330_9W_3E This gives 7s with a cold cache. Discourse is working on improving this: [图片] The State of JavaScript on Android in 2015 is... poor blue_bookGeneral For several years now we’ve tracked the fact that, over time from 2012 onward, Android JavaScript performance has become wildly divergent from iOS JavaScript performance. And not in a good way. To give you an idea of how divergent it has become, try: http://emberperf.eviltrout.com Complex list Ember 1.11 This is the benchmark most representative of Discourse performance, and the absolute best known Android score for this benchmark is right at ~400ms on a Samsung Galaxy S6. That doesn’t seem …

ok, so you know about. I currently switched to the js-less version. At this point an app makes sense … a lot!

As of October 2017, JS perf in Android / Chrome is substantially improved, probably 1.5x - 2x speedup. As of June 2018, Qualcomm has semi-competitive (iPhone 6s territory) hardware with the Snapdragon 845. It looks like their new release coming in 2019, the Snapdragon 855, will be close to iPhone 7 performance. We do have to wait for the vast bulk of old Android devices to cycle through the market, unfortunately. I expect that will take another 4 years.

I find my really dodgy 50 dollar android somewhat usable these days

For example I’m rocking a Pocophone F1 which costs $299, has the Snapdragon 845, and it’s a breeze to browse Discourse using it (I do it everyday :wink:)

Anything at Snapdragon 845 level or higher is going to be very solid for Discourse.

i have a few users on android phones using the chrome browser complaining of slow site loads, only very recently, one since the last upgrade only. Anything changed which might effect this?

Discourse mobile slow on 2013 Android phone

Product Support

zogstrip (Régis HANOL) 2016 年3 月 30 日 20:03 4

Well, you have to take into account the speed of light here.

You are comparing the speed between Frankfurt San Francisco and Frankfurt Amsterdam.

话题		回复	浏览量
The State of JavaScript on Android in 2015 is... poor General	285	153496	2022 年12 月 18 日
Android "slow_platform" per page setting Product Support	2	1342	2018 年7 月 11 日
Discourse Loading Time Feature	10	3379	2021 年2 月 5 日
Discourse poor on mobile has 5 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page Product Support performance , mobile	3	1602	2015 年11 月 5 日
Discourse Mobile App - Performance Issue (possibly)? Product Support	6	578	2018 年8 月 27 日

Discourse mobile slow on 2013 Android phone

相关话题