Connect Web workout app COMICALLY SLOW on all browsers.

I'm not sure what's going on in the last 48 hours, but the connect web app is nearly unusable for the sake of customizing my workouts, on the following browsers:

  • Chrome
  • Firefox
  • Edge

The specific symptom I'm seeing, is that customizing strength training workouts (probably all others, haven't tested) seems to make every interaction take 5x longer than it should:

  • Clicking 'edit step' on a workout step takes 2 full seconds to complete.
  • Typing a SINGLE letter in the 'Notes' box for a given step takes 2 full seconds to complete PER LETTER.  So a sentence can take MINUTES.
    • Interestingly, a deletion also takes 2 seconds, even if you're deleting everything.
    • Similarly, pasting an entire paragraph takes 2-3 seconds.  So, it seems like the added overhead is 'per interaction'
  • Deleting a step takes 6 seconds, for some reason.
  • "Dragging" a step around takes 2 seconds of holding the mouse to register the 'grab', then another 2 to register the 'placement'. 
    • The dragging itself seems to have normal responsiveness, if you wait the 2 seconds required to 'grab'.

It's as if your entire GUI is doing something in the background for everything it thinks is an 'input' that adds overhead to every minute action.  

The whole thing is effectively coated in molasses and SO frustrating to use right now. 

I've done a little casual troubleshooting to get you guys started fixing this showstopper of a bug:

  • I've ruled out any sort of browser, plugin, vpn, internet issue or performance issue on my end.
    • With chrome, I even went as far as disabling EVERY plugin I had to test, no change.
  • No other app seems to have these problems.
  • What's more, when I open the dev console in one of these browsers, and do any particular interaction outlined above, I usually don't see any new requests being done to the server.
    • Opening a step for editing shows a single, fast request... but typing into the notes box for example (by far the step most impacted by 'overhead' here) shows NO new requests.
    • This implies that the issue is with recent changes to the page's javascript, or some other static client-side resource, rather than the backend server.


If you need a chrome dev trace or something of that nature to better troubleshoot this issue, please reach out to me privately and verify you're with Garmin.  I would prefer not to post such a thing in a public forum.