@ABC123 It sounds like the underlying issue isn’t that JavaScript is “too fast,” but rather that the page is relying on resources or DOM elements that aren’t fully available when the script executes. The fact that a hard refresh (Ctrl+F5) resolves it...
