: "Time on site" value for a month in Google Analytics is different based on the number of months viewed We have to check monthly reports for server response time on Analytics, and I noticed
We have to check monthly reports for server response time on Analytics, and I noticed something that makes very little sense to me.
When looking at a monthly report for last month (April 2017), we get a server response time of 2.10 secs, due to a spike from a single user.
When looking at that same month on the spectrum of the site's entire life (from Jan 2014 to May 2017) April 2017 is displayed as 1.17secs.
In fact, looking at a 4 year spectrum, the values look different all around.
What exactly should I trust on the server response time calculation?
Can anyone explain to me how they calculate these values and why they would be different depending on the time period we extrapolate them from?
More posts by @Kaufman445
1 Comments
Sorted by latest first Latest Oldest Best
The problem with the Analytics server response metrics is they are very subjective.
The best thing about the Analytics server response metrics is they are very subjective.
These measurements are from users with different internet connections in different places, if your user-base is small then expect wild variation when someone from very far away on a satellite connection connects vs someone local on fibre. This isn't just measuring the time it takes for your server to wake up and send HTML - it's the time it takes for that initial packet to get there.
This could be the sign of an issue - or it could not. As long as things seem healthy from your end, don't worry too much. If you are running your own server infrastructure or using a small provider then I would encourage you to do a geographical breakdown just in case there are network issues.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.