This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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.

  • Issue persists.  Tested on my mobile phone, using both wifi and LTE, and forcing the 'desktop site' in the browser (Chrome for Android): exact same symptoms.

    Has to be the site's Javascript or something.

  • I'm not having all of these issues but I can def confirm that typing in the Notes field is extremely slow. Pressing Edit Step does seem to be slow as well.

    If anyone from Garmin is reading this, it looks like the first input event handler attached to div.content.page.workoutPage is the culprit for the slow notes field. If I delete this event handler, then I can type normally, but the character count - e.g. 20/200 - is no longer updated on every keystroke.

    It seems that maybe the code which updates the character count is the ultimate bottleneck here. Here's how I tested:

    1) I delete the event handler mentioned above.

    2) I ensure I deleted the correct handler by typing in the Notes field and observing that there's no delay

    3a) If I give the notes field focus by clicking on it, then press TAB to make it lose focus without typing anything in the field, the focus rectangle immediately moves to another field

    3b) If I give the notes field focus by clicking on it, type in a few characters, then press TAB to make it lose focus, there's a noticeable delay of about 1 second as the character count is updated, before the focus rectangle moves to the other field.

    https://postimg.cc/xq5QBG0n

    https://postimg.cc/fJgNRwtP

  • I can confirm that deleting the event handler mentioned by FlowState seems to improve the performance of inputting characters into the notes box significantly.

    However, the issues persist elsewhere in the GUI as mentioned in the original post, even after this specific tweak.

    I've delved a little bit deeper using chrome dev tools' performance tab, and it looks like for the keypress, and all other events that seem 'slow' from my testing, it can be traced to the eventual call of the 'translate' function.

    I typed up a post explaining this at-length, but the forums keep rejecting it; looks like your cloudflare WAF is a little strict.

  • I typed up a post explaining this at-length, but the forums keep rejecting it;

    forums.garmin.com/.../forum-problems-nov-2024

  • Ditching the explanation, doing just the links.  That WAF is pretty spicy right now, I'm not even sure where to start sanitizing my reply for it.

    Text box test picture: https://postimg.cc/fS3XvYh8

    Drag and drag test picture: https://postimg.cc/D8JdQ3v7

    Link to trace file: https://file.io/xT8dL7Kjzyac

  • Testing today, issue seems to be resolved.  Connect Web is still not the most responsive app I've see: every input event still seems to take around 292ms (which adds up when typing out a full sentence, for example), but it's... not totally unusable anymore.

    Room for improvement.  The 'CS' function is getting called twice by the 'XC' function now, taking around 143 MS per run.  Still markedly better.

  • I take it back... it's even WORSE today than it was before.  Once again, it's the chain of calls leading up to a particularly time consuming translate call that seem to be to-blame:  https://postimg.cc/9RS35Gdk

    Does anyone from Garmin even read these forums?

  • Does anyone from Garmin even read these forums?

    It can occasionally happen, but I would not rely on it. Much better speaking to them directly through their website at https://support.garmin.com

  • Thanks, I kept running into the KB interface instead of the support request interface... they look weirdly similar.

    Sounds like the issue has been escalated.

  • You can also send an email directly to [email protected]. At least it’s worked for me in the past. Ppl seem to feel that it’s much better to use the online chat option on the website though.