GA Asynchronous tag increases time on site?
11 views
Skip to first unread message
Merriam, Trisha
Feb 8, 2011, 9:23:35 AM2/8/11
to marketm...@googlegroups.com
We installed the GA asynchronous tag on our site in mid-Jan. Before the tag, our avg. time on site was under 2 minutes. After the new tag, our time on site is over 10.
That’s a pretty number, but utter nonsense. Has anyone else had a similar experience?
Trisha Merriam
Web Analytics, SEM, SEO
D&B Digital
650 Townsend St., Suite 450
San Francisco, CA 94103
Direct: 415.694.5051
Cell: 650.283.0591
Fax: 415.694.5001
Email: merr...@dnb.com
Edmon Moren
Feb 9, 2011, 6:18:07 PM2/9/11
to MarketMotiveWA
well, the asynch tag is supposed to load up to 30% faster, and I have
watched a few presentations on how pageload times have a dramatic
impact on how much people engage with your content, but the jump seems
very high to be explained only by this. Perhaps there were other
changes ( new hosting, new content, revamed CMS, different traffic
sources etc.) that could also explain this?
> Email: merri...@dnb.com<mailto:merri...@dnb.com>
> [cid:image001....@01CBC758.B6FE26F0]<http://dnbdigitalmediakit.com/>
>
> image001.gif
> 3KViewDownload
watched a few presentations on how pageload times have a dramatic
impact on how much people engage with your content, but the jump seems
very high to be explained only by this. Perhaps there were other
changes ( new hosting, new content, revamed CMS, different traffic
sources etc.) that could also explain this?
> [cid:image001....@01CBC758.B6FE26F0]<http://dnbdigitalmediakit.com/>
>
> image001.gif
> 3KViewDownload
ika abd karim
Feb 9, 2011, 8:29:29 PM2/9/11
to MarketMotiveWA
I have installed the GA Async in my personal website, and the avg time
seems to be fine.
Could you explain what you mean by "before the tag"? How do you
capture the avg time "before the tag"?
Did you upgrade from ga.js version to async version?
Usually when there are weird data reported in GA, i would dig on the
data to help me find the root cause of the issue.
Perhaps (if nothing else change on the site per Edmon note above),
what you can do:
- verify the avg time over 10 no which pages? is it certain pages, or
on all.
- verify the source of traffic for the effected pages
- go to the page, as try to capture if there is anything seems catchy
(would contribute page weight) on the page
- good also to measure the page load time by using Firefox add in tool
like Page Speed or Yslow.
Shakirah Abdul Karim
Analytics & SEO
seems to be fine.
Could you explain what you mean by "before the tag"? How do you
capture the avg time "before the tag"?
Did you upgrade from ga.js version to async version?
Usually when there are weird data reported in GA, i would dig on the
data to help me find the root cause of the issue.
Perhaps (if nothing else change on the site per Edmon note above),
what you can do:
- verify the avg time over 10 no which pages? is it certain pages, or
on all.
- verify the source of traffic for the effected pages
- go to the page, as try to capture if there is anything seems catchy
(would contribute page weight) on the page
- good also to measure the page load time by using Firefox add in tool
like Page Speed or Yslow.
Shakirah Abdul Karim
Analytics & SEO
tmerriam
Feb 10, 2011, 5:36:14 PM2/10/11
to MarketMotiveWA
Yes - I upgraded from ga.js to async, so I have historic time on site
data. I also run Omniture in parallel, and OM reports absolutely no
change in time on site. All signs point to a reporting error on GA.
I've found that running two analytics solutions in parallel is
extremely useful - no solution seems to be error-free, and it helps me
to avoid wasting time looking for the causes of non-issues.
data. I also run Omniture in parallel, and OM reports absolutely no
change in time on site. All signs point to a reporting error on GA.
I've found that running two analytics solutions in parallel is
extremely useful - no solution seems to be error-free, and it helps me
to avoid wasting time looking for the causes of non-issues.
OD
Feb 11, 2011, 8:12:12 AM2/11/11
to MarketMotiveWA
Hi All,
I will throw out some other possibilities, which you may have already
cleared.
- Are you looking through a different or new profile that doesn't have
internal excludes?
- Is someone new viewing the site from a remote location for long
periods of time? Designers/content authors, etc...
- Have you ran a report to check js code for errors? http://sitescanga.com/
(this can scan async now)
- I am not familiar with Omniture but certain JS code does not play
nice which each other. Are the closing tags there (</>)?
- Was the old ga.js removed from the footer?
- If you are looking at the Top Content Report, is one section much
higher in time than another?
Good luck,
OD
I will throw out some other possibilities, which you may have already
cleared.
- Are you looking through a different or new profile that doesn't have
internal excludes?
- Is someone new viewing the site from a remote location for long
periods of time? Designers/content authors, etc...
- Have you ran a report to check js code for errors? http://sitescanga.com/
(this can scan async now)
- I am not familiar with Omniture but certain JS code does not play
nice which each other. Are the closing tags there (</>)?
- Was the old ga.js removed from the footer?
- If you are looking at the Top Content Report, is one section much
higher in time than another?
Good luck,
OD
Reply all
Reply to author
Forward
0 new messages