The discussion revolves around Discourse’s loading time, particularly in light of Google’s upcoming use of page speed as a mobile search ranking factor. outofthebox initiates the conversation, noting that Discourse’s mobile performance scores are suboptimal on Google’s tools. Daniel_Nevoigt questions the validity of these scores, comparing Discourse’s speed favorably to other platforms. Stranik clarifies that Google’s tools may not reflect the actual user experience, as they measure the initial load of a JavaScript application. codinghorror explains that Discourse’s initial load is slower due to its JavaScript-based nature, but subsequent loads are fast because only data is transferred. merefield and awesomerobot discuss the fairness of measuring first-load time versus in-app responsiveness, with awesomerobot emphasizing that Google targets only the slowest sites. j.jaffeux stresses that content quality outweighs performance metrics. sam provides comparative load times, showing Discourse performs well relative to other sites despite its initial load. edgarriba mentions a slow load on a free DigitalOcean plan and requests a progress bar plugin, which j.jaffeux points to a recently released solution. The topic is closed as outdated.
Well, the official part beside, I cannot see any slow working stuff with meta or other hosted discourse instances. Even my 1 core 2gb cloud setup is even faster than my Shopware Shopsystem which has page speed of 80%+. So, what is going wrong, Discourse or the google developers stuff?
Nature of the beast; we are a JavaScript application, so the app has to be delivered to the browser.
It is a bit like if you were measuring smartphone app startup times, including the time spent to download and install the app from the app store as part of the “startup” time.
What isn’t shown is that subsequent page loads are blindingly fast in Discourse because the app is loaded in the browser, and we only send API calls and json (the data necessary to render the page) down the wire.
I don’t think it’s completely unreasonable. Google’s job as a search engine is getting you the most relevant information as fast as possible — if a static HTML page has content of identical relevance they should probably favor that over downloading a web app… it’s totally likely you might not ever have a subsequent visit anyway (and if you do, I imagine that’s a bigger relevance factor than speed anyway).
Important to note that Google also reaffirms in their post that they’re only going to be penalizing the slowest of the slow… and more relevant content will likely always win anyway.
I have spent literally years following google good practices, building sites constantly scoring above 95% on every single rating tools google would give us and… I have seen countless sites with terrible scores and UX, ranking way better than me.
In the end it’s always the same, CONTENT IS KING, and perf/ssl/whatever will be a very small part of your ranking in the end. Not saying we are not committed to make Discourse as fast as possible. But I wouldn’t be too worried about this.
Given that Discourse is an entirely JavaScript based application I think it stacks up quite well even against traditional “non JS” sites.
Despite the slightly slower initial load on mobile, using Discourse on mobile is FAR more enjoyable than other sites cause it has only a tiny network footprint while browsing around.
There is no chance Discourse is going to be punished here due to any of the numbers I am seeing, though as always we strive to make Discourse faster and better every release despite needing to ship an entire “engine” to a client to run the forum.