Hey @vlntnt,
We’re sorry for the lack of details here.
My colleague provided a workaround code because he recognized the issue with the offset. It happens if there’s a Sticky Bar with the Position of Relative. The code he provided sets the Sticky Bar Offset manually. If the Sticky Bar is set to Absolute Position, the offset will work and the code is not needed. It’s not applicable for your case though as you have another Bar below the Sticky Bar so that is why the code is needed.

Now as to why the issue is still happening even after adding the code. That is because something in your content is dynamically loaded so it messes up with the sticky bar position calculation. It’s not because you have to wait for the page to fully load. It’s because something in your content will load only if you have scrolled to the area where the dynamic content is. Please watch the video below closely and you’ll see that the offset works if you have scrolled through all the contents from the header to the footer.
With that said, there is an issue with our theme if the Sticky Bar is Relative Position. But, there is also an issue or a conflict with your content being dynamically loaded which messes up our theme’s sticky bar calculation.
What that dynamic content is, we don’t know. It could be lazy loaded images or content loaded using Javascript.
The ulitmate test you can do is save your page as a template using the Template Manager then load your page template in a test page. In the test page, remove sections 1 by 1 while testing the jump link offset each time. The last section you remove that makes the jump link offset work is the culprit. You must not use it in your page.
It would also help, if you disable ALL 3rd party plugins (including optimization plugins that use lazy loading) while testing. If you can’t do that since your site is live, copy your site to a staging server then do all the test in staging.
To summarize, there are 2 factors causing the issue:
- a possible bug in our theme (theme issue)
- dynamically loaded content (not a theme issue and this one you should find and fix)
Thanks.