hmmm… i wonder if what some of you are describing is related to https://forum.inaturalist.org/t/out-of-memory-errors-in-identify/14774/5? that problem is related to a probable memory leak or bloat on the Identify screen, which manifests itself after you go through many pages of observations and can be mitigated by refreshing the Identify page occasionally.
to figure out if it’s a memory thing or a network thing, you could do the following:
- if it’s a network thing, if you open your browser’s developer tools and go over to the network section. once that’s open, take the action that you expect to be slow. if it takes, say, 10 seconds for the page to respond, and you see the last network request took 10 seconds to complete, then it’s possible something is happening between your connection and iNaturalist.
- on the other hand, if you’re on a Windows machine and open up your task manager, then on the processes tab, make sure you have the more details section option selected, then if you see memory usage get up to and stay near 100% while you’re experiencing problems on the page, then the problem could be a possible memory leak. if you refresh the page, and the memory usage drops significantly, then that’s more evidence of a possible memory leak on that page.