Example: open https://avan.tech/item69067#threadId76457 in a new tab (or any link with an anchor in it)
Result: it loads the page, waits a few seconds, and then scrolls with an animation all the way to the final position.
It would be preferrable to jump directly to the comment without any scrolling animation, as it is bad for accessibility (i.e. it is a recipe for motion sickness https://en.wikipedia.org/wiki/Motion_sickness sensitive people in particular, but I would say even for _anyone_ there is no clear justification for this slow and power-inefficient approach)
Why use fancypants javascript to introduce an artificial delay and animation for this, instead of standard HTML anchors? I bet this was done because you are loading comments async, instead of loading them in one block as part of the page's DOM, like other issue trackers / systems out there. But it also means your comments will never work without javascript, etc.
I'd suggest loading the whole page at once, especially when an anchor is used in the URL or javascript fails, or, if that's 100% absolutely technically infeasible, then instead provide a loading ghost/skeleton wait overlay (during full page load) before positioning the user exactly at the final position instead of using any animated scrolling motion.
If you need a client for this: ask any big public sector client, as they typically have universal accessibility requirements that could justify this.