[stonewareslord]

With javascript disabled on mobile, you just get a header with links that don't work and "best viewed with JavaScript enabled" even on the official https://try.discourse.org/ site

What I don't understand is why discourse can't serve up content that isn't interactive. I get lazy loading if there are >1000 comments on a post, but for anything else, static content should be perfectly fine. Even when you have js on, ctrlf doesn't work because of dynamic loading so the site has to hijack the shortcut with different interaction patterns (pressing enter doesn't go to next result, it loads a separate page).

I just tested with the 999 comment post on that site. First page load with no cache is 5.98MB (1.25MB) and took 5.76s load time. Holding the end key to get to the bottom until I hit the last post downloads a total of 1.91MB (718KB transfer) and takes 70s! That's including all the pictures. That cannot be better than than loading all text and optionally deferring all img loads, right?

[zelphirkalt]

"Lets not load so much static content all at once, it will be slow!", but then serve megabytes of JS dependencies and perhaps some web fonts for good measure. Unfortunately this is becoming more common.