reduce speed in v3.0.0
-
Hm... it's not the first time I've heard about this. @phenomlab I think also mentioned something during the alpha phases.
It's worth exploring if there's something tangible here. Do you feel that there is a slowdown in actual "time to first paint/first contentful paint"?
Anecdotally, it may be a delay in "time to interactive". It seems maybe sometimes the page will load but there is a delay in processing the client side JS and clicks don't respond quite as quickly as expected.
The band-aid to this, of course, is to slap a blur filter and a loading message like Discourse does... but that is admitting defeat isn't it
-
@julian i m also feel it but it was on alfa versions. i told it to @phenomlab when we checked his beta web site but cr and v3 stable version dont have any speed problem. its my opinion of course. maybe Mark can give more information about it.
-
Three runs against v3 Harmony (localhost) yields the following. Not too shabby.
v3 Harmony (community.nodebb.org)
Considering that Lighthouse scores aren't the be-all-end-all of performance metrics, at least we pass those contrived tests with flying colours.
-
@julian said in reduce speed in v3.0.0:
Do you feel that there is a slowdown in actual "time to first paint/first contentful paint"?
Yes, although these metrics should always be taken with a pinch of salt. In some cases, as @baris has highlighted, the presence of plugins that scan the page looking for actions (such as iFramely etc) will slow down rendering also. However, I see iFramely for example as something of a cosmetic necessity as it makes standard links look pretty and in line with the modern web.
However, all of this comes at a price in terms of site speed. If you are using iFramely, remove it, and see how much your page speed will improve. Essentially, page speed is more about user perception than any bot. By this, I mean a bot can report it taking 1.5s to open your site, yet when a human visits, this isn't the experience they get. Google PageSpeed is the worst for this as it uses mobile by preference, and thinks everyone is using 56k modems
The generally accepted standard is for pages to load within around 500ms. Any higher than that, and you risk increasing the churn rate - I for one will not wait more than 2 seconds for a site to load - unless there is good reason, and I cannot get the information I want elsewhere.
For want of a better phrase, it's easy to get over passionate about page speed seeking the holy grail of CLS and LCP, but this will have a negative impact on the user experience which comes first over any bot. Real users will also wait if they are returning because they want to. Google only crawls your site - it doesn't actively read, comment, and interact. There are a number of "best practices" that can be applied, and all of these are industry standards. However, I care more about the security of a website rather than how fast it can load. I've seen so many times where people spend a day tweaking a WordPress website only to find they are doing it as cached user and not incognito, meaning the changes they applied broke the site 4 hours ago, and they have no idea how to fix it, so just reverse everything.
In a nutshell, if your site takes more than a second to load, it's a high chance you are calling an external library that you can either host locally, or remove altogether - or, your hosting provider is inferior and you should change it.
-
J julian forked this topic on
-
@julian
When typing in topics or private chat, it is typing slowly, just like when the system is running low on RAM, there is a delay between typing and appearing on the screen.
Most of our users have reported this issue.
While chatting, the typing speed gradually decreasesOr when they stay on a page, the replay buttons,... don't work and they have to open another tab
And sometimes when type something after a delay the word was duplicated
-
@inspiring interesting. I'm also getting reports of this via users of sudonix.
-
For me Notification and chat menu takes long to load.
-
Yep same probleme here on my dev instance
-
@inspiring @phenomlab are these long-running chats? Do the issues go away when you start a new chat?
-
@inspiring When you say "a few messages", are we talking 10 messages, 100, or 1000? It definitely sounds like there's some sort of scale issue going on.
NodeBB used to naively load every message in the chat room when opened, but we fixed that awhile back. The fact that you're seeing issues when "typing" is a little concerning too.
Desktop users? or mobile only?
-
B baris referenced this topic on
