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

Garmin fails to Synch with Noom App

Former Member
Former Member

I have been trying for weeks now to synch my new vivofit 4 with my Noom app. The problem always arises when it tries to load the Garmin pages. I have plenty of screen caps I can share. Why are all of Garmins webpages so slow and poorly functioning? I’ve tried with two iPhones a and two separate computers. I’ve complained about it being impossible to access the site several times. Couldn’t even buy my new tracker from Garmin’s site because it would never load.

  • Why are all of Garmins webpages so slow and poorly functioning?

    Personally, I have no problems acessing any pages on any of of Garmin's websites (garmin.com, support.garmin.com, connect.garmin.com, or forums.garmin.com). They all load pretty instantly. Only exceptionally (perhaps once in a few weeks) it happens that there are some slow downs. You can then check the system status at https://connect.garmin.com/status/ to see some details.

    So if you are expereincing permanent slow downs, the problem is probably not with Garmin servers, but rather with something on the way to you, or at your location (perhaps a malconfigured router, or a firewall filtering some parts of the communication). What country are you located in? Do your friends have the same problems?

  • Former Member
    0 Former Member over 4 years ago in reply to trux

    I’m in the US.  I work from home and my livelihood depends on my internet access.  Garmin sites are the only sites I have trouble with.  I can leave the house and use my data on the phone and have the same problems.  I don’t know anyone else personally with a Garmin they are trying to synch.   

  • You can always try to analyse what exactly causes the delays, localizing the problem better. On a computer, open DevTools in the browser (F12 or Ctrl+Shift+i), click the Network tab an load the page. When it is visually loaded, click the red button on the extreme left of the menu to stop further loading of diverse scripts, that continue to be called, and which would complicate the analysis.

    In the column Time, you can then see the loading times of individual elements of the page, and in the last column Waterfall  you see the sequence of the loading. Click on the header of that column to have the elements sorted by the order of loading, and then click on the lidividual elements to see the details. In the example below (loading the Personal Records page on Garmin Connect Web) the most important element is the PersonalRecord.default.... - the third row from the bottom. It started to load 450ms after the initial request, and loaded after some 390 ms. All together some  840ms - it is not instant, like it can be at symple static pages, but at dynamic pages with a huge number of elements, it is a rather standard loading time.

    So try it yourself - perhaps it can reveal that some of the elements are lagging more than others for some reason.