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.
You can see there is timerange with 100% cpu.
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.
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:
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 
)
Anything at Snapdragon 845 level or higher is going to be very solid for Discourse.
Einige unserer Android-Nutzer mit dem Chrome-Browser berichten seit Kurzem von langsamen Ladezeiten unserer Website – einer davon erst seit dem letzten Upgrade. Gab es Änderungen, die dies beeinflussen könnten?
Stelle sicher, dass du die neueste Version verwendest. Wenn du hinter einem Reverse-Proxy oder einem anderen seltsamen Proxy wie Cloudflare stehst: Es gab kürzlich einen Fehler, der verhindert hat, dass das Fallback von Brotli auf gzip funktioniert. Das ist unerträglich angesichts der daraus resultierenden Größe der Payload-Datei.
Alles auf dem neuesten Stand, ohne CDN oder Proxies. Auf meinem iPhone mit Safari funktioniert es einwandfrei. Hat jemand anderes ähnliche Probleme? Das einzige Plugin, das ich habe, ist das für Werbung, und ich verwende es derzeit gar nicht.
