Ahhh ok! Sorry about the false alarm!
Thanks Damian.
It wasn’t just P3 that reported the issue. http://www.webpagetest.org/, https://tools.keycdn.com/speed and https://www.dareboost.com all reported that the Google Maps APIs called by the plugin were adding 2.6 seconds to every call, plus the additional 2 seconds added to load the geotargeting JS files.
but then everything is saved into a session variable
Hmm.. this should make sense, but I see the Google maps APIs called every time.
I have WP_CACHE enabled and still see the “Twitter did not respond error” constantly – in fact, it hasn’t worked for me at all.
Right now, I’m using WP 2.9.1 and Wickett 1.0.2.
