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.
페이지 속도 점수보다는 크롬 사용자 경험 보고서(CrUX) 결과에 더 관심이 있습니다… 저도 같은 불만을 보고 있습니다… 실제 사용자 경험을 더 빠르게 만드는 팁이 있다면 알려주시면 좋겠습니다. 결국 방문자가 사이트를 상호작용하게 만드는 것은 빠른 로딩이고, 뒤로가기 버튼을 누르게 만드는 것은 느린 로딩이니까요… 이러한 이탈은 사용자가 사이트에서 원하는 것을 찾지 못했다는 신호를 구글에 보내며, 이것이 랭킹 하락으로 이어집니다… 페이지 속도 점수 자체 때문이 아닙니다. 수정: 구글은 속도 자체를 랭킹 요소로 사용한다고 말하지만, 정확히 어떤 지표가 이를 좌우하는지는 잘 모르겠습니다.
그래서 이 사이트가 Fastly를 CDN으로 사용하고 있지만, Chrome 사용자 경험 보고서에서는 여전히 “느림” 속도 평가를 받는 것 같습니다… CDN을 사용해도 "보통"이나 “빠름” 등급으로 올리는 것이 사실상 불가능할까요? 동적 콘텐츠가 너무 많기 때문인 것 같습니다…
