Being On 4 cores of Intel CPU there is significant drop of speed after i updated the discourse.
I recently Updated my discourse (its pgsql database was also updated) and now its very very slow. 8GB Digital Ocean Droplet.
Results Before this update were - Mobile 75/100
I do not have any extra javascript in the page, when i tested, No Alexa, Webmaster etc scripts. Its a serious issue in Google SEO.
Discourse Team Can you please release a light version with less features for Better speed and Performance.
Or
Please guide me how can i improve upon it.
I also feels the speed difference when i Browse My own site old/new version in incognito mode (Not tested with google.)
I don’t think it would be a good idea to nuke out functionality of discourse in the name of Google pagespeed insights. In my personal opinion, pagespeed insights don’t really focus upon SEO but they rather focus upon the UX of a website.
First load may be a problem (only because all the resources are being loaded from server instead of cache) but once that’s done, there shouldn’t be any performance penalty.
Note that in your tests, Google wasn’t even able to provide an accurate metric of real-world performance… and only looked at possible optimizations. Those possible optimizations don’t seem to take into consideration that Discourse is a JS app.
I think the team is always looking for ways to make Discourse faster… but there’s little evidence that this is a serious SEO issue. Here’s some information from Google on their 2018 Page Speed Update, which is probably the most significant impact Page Speed Score has ever made on ranking:
The “Speed Update,” as we’re calling it, will only affect pages that deliver the slowest experience to users and will only affect a small percentage of queries. It applies the same standard to all pages, regardless of the technology used to build the page. The intent of the search query is still a very strong signal, so a slow page may still rank highly if it has great, relevant content.
So on the one hand, they don’t care that we’re a JS app and apply the same standard to everyone (potentially something to look out for)… but on the other hand this change only impacts a small percentage of queries and content relevance is still the primary metric for ranking.
I also feels the speed difference when i Browse My own site old/new version in incognito mode
Are you able to provide any additional details? Which version were you on previously? Did you use any of the Network tools in the Chrome inspector to measure load speed?
None of the recommendations are really relevant to us, sure we can shave off a few bytes from avatars and some tiny js scripts, but there is nothing substantial here.
Me preocupa menos la puntuación de velocidad de la página y más los resultados del informe de experiencia de usuario de Chrome… Veo las mismas quejas de mi lado… Me encantaría que alguien compartiera consejos para hacer que la experiencia real del usuario sea más rápida, ya que esto es lo que finalmente lleva a los visitantes a interactuar con tu sitio (carga rápida) en lugar de pulsar el botón de retroceder (carga lenta)… Esos rebotes envían una señal a Google de que la gente no encuentra lo que busca en el sitio, y eso es lo que provoca caídas en el posicionamiento… no la puntuación de velocidad de la página en sí. Edición: Supongo que Google sí dice que utiliza la velocidad en sí como factor de posicionamiento, pero no estoy seguro de qué métrica específica impulsaría esto.
Así que supongo que este sitio usa Fastly como CDN, pero aún tiene la calificación de velocidad “lenta” en el informe de experiencia de usuario de Chrome… ¿quizás sea simplemente imposible alcanzar una calificación de “moderada” o “rápida” incluso con una CDN? Supongo que se debe a la naturaleza de tanto contenido dinámico…
