Low bandwidth users

Experiência do Usuário
1

Continuing the discussion from Make Discourse play nice with the Wayback Machine:

[quote=“codinghorror, post:7, topic:34579, full:true”]

Where are you getting this data from? [/quote]

Measuring from my own site on a text-only topic, no cache, I’m getting 4.3 MB. At 56k simulated speeds in Chrome dev tools, it churns for 15-20 minutes and times out, less than a quarter of it loaded. (I’m still trying to find out why my site is heavier than meta… ) I have yet to successfully load a page at this speed.

I’m not saying there are lots of dial up folks out there. But there are a few left, by choice or necessity.

Verizon inherited about 2.3 million AOL dial up customers, according to Time magazine. And 3% of Americans still use dial up at home, according to this research group.

On top of that, folks throughout the developing world have limited access speed and data caps - not to mention under-powered hardware. A simpler, lighter interface will open the door to them as well.

Obviously we aren’t catering to these folks… but since we already serve up an stripped down HTML version, making it functional will let them participate.

Here’s some other big sites that present a functional stripped down version.

Facebook now has “Facebook Lite”: http://techcrunch.com/2015/06/04/download-facebook-lite/

Gmail has basic HTML: https://mail.google.com/mail/?ui=html

Twitter with javascript disabled redirects to https://mobile.twitter.com, and is functional.

Google Search with javascript disabled redirects to an older but functional version (and slims down from 362kb to 62kb).

2

Is that without any form of built in HTTP gzip compression? That does not seem correct to me at all. Remember text compresses at 70-80% typically.

2 curtidas
3

Ah! Thanks for that… Turns out gzip was not working. We’re down to about 900kb now, and things are much more snappy!

2 curtidas
4

The irony is that Discourse, being a JavaScript app delivered over HTTP, is a best case performance scenario for a severely bandwidth constrained user. The first load will be the chunky, but all highly compressible, JS text of the Discourse app – and every subsequent request is for only the JSON data necessary to render the requested view.

At no point is a “new web page” send down in its entirety to the user.

But do not take my word for it. Feel free to measure it yourself – with a normal, gzip compatible http connection – and see.

(It is true that first load perf will not be amazing because we send the app in that first payload. But all text.)

4 curtidas
5

You might find this an interesting read:

https://meta.discourse.org/t/blog-post-is-high-bandwidth-required-to-read-a-discourse-forum/26995?u=erlend_sh

(please excuse the slightly aggressive language; it’s not directed at you! At the time of writing, there was a very vocal minority of people who were crusading against the advent of JavaScript as a web technology without presenting any factual data)

4 curtidas
6

After first load, Discourse is an exceptional low bandwidth site. I can’t think of any site that does better in these scenarios.

The first load can be quite rough though, since you need to pull down the whole app bundle. We are looking at improving first load time in various ways in 1.8 or maybe 1.7 depending on timing.

5 curtidas
7

Music to my ears. We have thousands of users in LatAm on spotty 3G connections who find us via search engines, but it’s hard to know how many we lose because they dont wait for the great web app experience to load :slight_smile:

2 curtidas
8

It is definitely quite high up on our list, right under …

:kissing_heart:

4 curtidas
9

6 anos depois e estou curioso sobre um ponto de entrada leve também. Não sou o administrador do nosso fórum Discourse, mas faço a maior parte do triagem de perguntas de suporte.

3 dias atrás, atingi meu limite mensal de dados e fui limitado. Nos 3 dias seguintes, fui essencialmente banido do site. A tela ficava na primeira tela em branco com os 5 pontos de progresso em um loop aparentemente interminável.

Felizmente, eu tinha o modo de lista de e-mails ativado nas preferências da minha conta. Assim, pude continuar respondendo aos visitantes.

A pergunta de solução de problemas acima sobre se o gzip estava em execução é intrigante. O site de repente teve uma animação de pontos de progresso há alguns meses e a página de inicialização passou de uma contagem de 4 para mais do que o dobro disso.

Existe um teste simples para determinar se o servidor está entregando conteúdo com gzipping? Ou quanta dados está sendo passada?

1 curtida
10

Se você estiver em nossa hospedagem ou usar a instalação oficial do Docker, gzip e brotli estarão habilitados por padrão.

Você pode testar seu site em https://www.webpagetest.org/ para confirmar, ou simplesmente dar uma olhada nas ferramentas de desenvolvedor do Chrome/Safari ou Firefox.

3 curtidas
11

Talvez pudesse haver uma entrada de emergência leve?

Que tivesse um login de conta que levasse a uma tela de gerenciamento de conta de baixa largura de banda que tivesse apenas 2 opções: ativar/desativar modo de lista de e-mails e enviar por e-mail um resumo de atividades da última hora/dia.