WordPress.org

Ready to get started?Download WordPress

Forums

[Plugin: Google Analyticator] GA in header instead of footer despite correct (3 posts)

  1. Yalla-one
    Member
    Posted 4 years ago #

    I am using Google Analyticator on a few themse by StudioPress. They all have the
    <?php wp_head(); ?> just above the </head> section of the header.php, but Google Analyticator still inserts the GA code in the header instead of at the bottom of the page.
    This slows down the page load and is thus undesireable.
    In previous versions this has not been a problem. Is there another solution to this apart from the one discussed on the FAQ section of Ronald Heft's support forum, as those solutions clearly don't make a difference in our case?

    Thanks in advance

    http://wordpress.org/extend/plugins/google-analyticator/

  2. cavemonkey50
    Member
    Posted 4 years ago #

    If you're running 6.1, yes, the tracking code is in the header, but this is by design. 6.x uses a new version of Google tracking code called async tracking.

    Basically, instead of loading the tracking code in order with the page (like previous versions of the tracking code), the tracking code is loaded in parallel at the same time. A browser visiting a page with the async tracking code will load both the page and the tracking code at the same time without conflicting. This means that even if Google's servers fail, the page content will load just as fast as if the code was not even on the page.

    The reason for now placing this code in the header is it increases the reliability of ensuring visitors are tracked. Previous versions of the code could miss visitors if they navigated away from the page before everything loads. Since there are no issues with slowing the page like previous versions of the code, the tracking code is placed at the top to give it a higher chance of loading before navigating away.

    You can read more about the async tracking code here: http://code.google.com/apis/analytics/docs/tracking/asyncTracking.html

  3. Yalla-one
    Member
    Posted 4 years ago #

    Great response - THANKS! I might have missed this somewhere, and if so I apologise. If not, you might want to make this a number one for the FAQ section - I read your FAQs at your website and got the completely wrong impression.

    Thanks again!

Topic Closed

This topic has been closed to new replies.

About this Topic