kor
Restricted (50-70%)
- Impact
- 1,673
Are you secretly running miner?
That shouldn't be the case when browsing NamePros. Our site is designed to work on low-end devices.High CPU usage is usually for hardware issues or an outdated operating system. Try a more powerful and newer device/desktop/laptop or add some RAM.
That shouldn't be the case when browsing NamePros. Our site is designed to work on low-end devices.
Yes. That's not to say the experience will be particularly enjoyable, but it'll be tolerable.Have your tried to browse NamePros on a 10+ years old cpu with integrated gpu and 2 gb ram? Those who complain about high cpu usage have usually such outdated devices which can't handle javascripts of today.
Those who complain about high cpu usage have usually such outdated devices which can't handle javascripts of today.
The keyword was "idle pages". It doesn't happen on active pages.
I'm using Safari 16.5 on MacBook Pro 2020 M1 (Ventura 13.4) and the same problem still occurs time to time.
I used to see it in Safari on an M1 device as well, but it's not an issue on iOS or in Chrome on macOS. I ended up switching back to Chrome since Safari doesn't support multiple profiles. There was no obvious cause, and Safari didn't provide any useful debugging info on the matter. (Edit: Typo)I'm using Safari 16.5 on MacBook Pro 2020 M1 (Ventura 13.4) and the same problem still occurs time to time.
Safari tells you exactly which website is causing the problem. It shows a notice at the top of the webpage.Find which processes are using most of cpu to make sure the issue is related to safari.
Eh?Websites that you can find at search result pages are usually safe.
That's rarely true, although in this case Safari isn't offering useful metrics when the issue occurs. I have a hunch it has something to do with Safari's buggy handling of some of the newer animation APIs, but that's purely speculation. Profiling doesn't show anything useful, which strongly suggests it's a Safari bug--if it were lousy JavaScript on our end, that'd show up during profiling.There is no easy fix from website side.
That's subjective and dependent on both use case and threat model.The most compatible and secure combination is firefox on a linux distro.
We're not going to ask users to buy new devices just so they can use NamePros. A MacBook Pro 2020 M1 isn't exactly a low-end device: it ought to have no issue. This is almost certainly a Safari bug that we'll either need to work around or report upstream.I would buy an extra laptop or build a new desktop or run linux+firefox combination virtually on the existing laptop.
That isn't applicable in this situation. NamePros has an in-house development team, and we test on all sorts of devices.Website owners are usually unaware. Even if they are informed about the problem, fix is usually very difficult and is not worth the effort and risks. Especially if the site script is a paid licensed one with encrypted codes, solution will be much more complicated or impossible. Websites, especially high traffic websites will be unable to solve the problem or will ignore the problem for an indefinite time period. Every change on website is a gamble for website owners. A tiny change may end up with lower traffic and/or revenue. Drops on search engine rankings particularly tend to be permanent.