# Discourse mobile slow on 2013 Android phone
**URL:** https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727
**Category:** Support
**Created:** [3월 29, 2016, 7:58오후 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727 "2016-03-29T19:58:00Z")
**Posts on this page:** 15
**Page:** 1
### Author:  [@lkwg82](https://meta.discourse.org/u/lkwg82)
#### Post date: [3월 29, 2016, 7:58오후 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/1 "2016-03-29T19:58:01Z")
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](https://forum.syncthing.net/t/ssl-certs-discovery-v4-vs-v6/6910).
I use the chrome on samsung s4.
(screenshot of developer tools), rendertime ~11s, without js ~1s (at home over wlan)
Thx in advance!
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [3월 29, 2016, 8:02오후 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/2 "2016-03-29T20:02:19Z")
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](http://meta.discourse.org) and [try.discourse.org](http://try.discourse.org) ?
---
### Author:  [@lkwg82](https://meta.discourse.org/u/lkwg82)
#### Post date: [3월 30, 2016, 7:57오후 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/3 "2016-03-30T19:57:22Z")
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.
1. [meta.discourse.org](http://meta.discourse.org): [http://www.webpagetest.org/result/160330\_8K\_592802ee00441a32192a5183af8ad1c9/](http://www.webpagetest.org/result/160330_8K_592802ee00441a32192a5183af8ad1c9/)
2. [try.discourse.org](http://try.discourse.org): [http://www.webpagetest.org/result/160330\_49\_024ca5619286ee2c338b3254e088d574/](http://www.webpagetest.org/result/160330_49_024ca5619286ee2c338b3254e088d574/)
3. [forum.syncthing.org](http://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
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [3월 30, 2016, 8:03오후 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/4 "2016-03-30T20:03:38Z")
> [@lkwg82](#):
>
> P.S. forum.syncthing is the fastest
Well, you have to take into account the speed of light here.
You are comparing the speed between Frankfurt ↔ San Francisco and Frankfurt ↔ Amsterdam.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [3월 30, 2016, 8:06오후 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/5 "2016-03-30T20:06:19Z")
This tests are using the chrome emulation, and not real devices too.
[http://mobitest.akamai.com/m/results.cgi?testid=160330\_9W\_3E](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](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889):
>
> For [several years now we’ve tracked](http://discuss.emberjs.com/t/why-is-ember-3x-5x-slower-on-android/6577) 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](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 …
---
### Author:  [@lkwg82](https://meta.discourse.org/u/lkwg82)
#### Post date: [3월 30, 2016, 8:17오후 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/6 "2016-03-30T20:17:29Z")
ok, so you know about. I currently switched to the js-less version. At this point an app makes sense … a lot!
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [1월 1, 2019, 9:29오전 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/7 "2019-01-01T09:29:01Z")
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [1월 1, 2019, 10:03오전 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/8 "2019-01-01T10:03:24Z")
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.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [1월 1, 2019, 9:55오후 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/9 "2019-01-01T21:55:47Z")
I find my really dodgy 50 dollar android somewhat usable these days
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [1월 1, 2019, 9:56오후 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/10 "2019-01-01T21:56:12Z")
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 😉)
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [1월 2, 2019, 6:26오후 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/11 "2019-01-02T18:26:28Z")
Anything at Snapdragon 845 level or higher is going to be very solid for Discourse.
---
### Author:  [@Shaneod](https://meta.discourse.org/u/Shaneod)
#### Post date: [7월 23, 2019, 7:44오전 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/12 "2019-07-23T07:44:36Z")
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?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [7월 23, 2019, 8:42오전 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/13 "2019-07-23T08:42:23Z")
Make sure you are on latest, if you are behind a reverse proxy or any other weird proxy like cloudflare, there was recently a bug that prevented fallback from brotli to gzip from working. And that’s excruciating given the resulting payload file size..
---
### Author:  [@Shaneod](https://meta.discourse.org/u/Shaneod)
#### Post date: [7월 23, 2019, 1:03오후 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/14 "2019-07-23T13:03:11Z")
Everything up to date and no CDN or proxies involved. Working fine on my iPhone with safari. Anyone else having similar issues? Only plugin i have is the ad one and I’m not even using it currently.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [1월 18, 2023, 5:10오후 UTC](https://meta.discourse.org/t/discourse-mobile-slow-on-2013-android-phone/41727/15 "2023-01-18T17:10:43Z")