The irony: performance.mark() call ends up being the most expensive one (by self time) in Chrome. I call it a few thousand times, but still I’d expect it to have less overhead.pic.twitter.com/Ejq4NPHk39
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Oh, and 500ms runtime for 1 million calls means 500ns per call. Not amazing, but not that bad, especially if a few memory allocations are involved. :(
500ms is what my profiler claims was spent under performance.mark on this testcase on my hardware in Firefox nightly.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.