Plugin Author
Damian
(@timersys)
To be honest I don’t like P3 plugin, it never return accurate results and I prefer other tools such as query-monitor to test my plugins and develop them.
I found that sometimes your server configuration or plugins affect more of P3 results than anything else. I currently ran a test on my local install and geotargeting plugin even don’t appear on the results. If you check the advanced metrics tab you will see actually how much time of your page load is taken by the P3 profiler. On my case the total page load time was 1.3631seconds and the profiler was taken 0.7929seconds , simple do the math 🙂
That being said it’s possible than on first page load the user experience a bit of delay because the country calculation is performed ( on pro version city, state, etc it’s also calculated) but then everything is saved into a session variable , so every other page load is using cached data instead of doing calculation over and over again.
Regards
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.
Plugin Author
Damian
(@timersys)
We don’t use Google maps API, that must be another plugin.
Regards
Ahhh ok! Sorry about the false alarm!
