Website page speed optimization was one of the essential benefits that marketers and web developers saw when the first version of Google Tag Manager was released. It was supposed to happen because tracking scripts would no longer be hardcoded but would be added through Google Tag Manager. So, does the GTM web container speed up your site?
This article will showcase how moving to the GTM server from Google Tag Manager Web Container can speed up your website. Please note that you won’t see any pagespeed improvements if you’ll combine server and browser tracking. For example, your site’s pagespeed won’t increase if you use both Facebook pixel and Conversion API. In this case, FB pixel will still work in user’s browsers and slow your site.
According to Google research, if a site takes longer than 3 seconds to load, 53% of users will leave. At the same time, on average, it takes 22 seconds to load the mobile page fully.
We live in a time when people use watch phones more than desktop devices, and smartphones account for more than 50% of all Internet traffic. But according to Google, the conversion rate on mobile phones is lower than on the desktop. That is why the website loading speed plays an essential role in meeting performance standards.
It is no secret that users expect a fast site experience. If the landing page is too slow, they’ll close the page or abandon the cart and move on to the competitors’ site. Today, in the mobile-first world, it’s critical to create fast-loading sites. Users want to have the ability to quickly open your blog and read the article, buy new clothes, check hotel reviews, and so on.
According to Amazon’s research, a 1-second delay in page response results in a 1% loss in conversions. That is equivalent to a loss of $1.6 billion in annual revenues for them.
As you can see, waiting for heavy pages to load can cost a lot for any company.
In 2020, Google released a server container for Google Tag Manager and Tag Manager 360. It enables advertisers to move third-party tags from their sites to a new server container hosted in the сloud servers. This way, the website can load faster, tracking can be more accurate, and data can be safer. Besides, moving tags to the server container can help you to solve this Google PageSpeed error – “Reduce the impact of third-party code — Third-party code blocked the main thread for 550 ms”.
If you move tags from the web to the server container, tags will be loaded directly into the server container, not inside the user browsers. This way, the page will load faster, and it will have a positive effect on the user experience. As you see, it can provide faster page load times, more security for your customer data, and more data management tools.
Tags in the server container only have access to information sent to the server. They do not have access to other information that users enter on the site. And since these tags are placed in your server container, you can understand which data tags are collecting information and where the information is sent.
For this experiment, I used a demo website and compared Google PageSpeed results when tags were added via the GTM web container vs. the GTM server container. Not all tags have the same impact on Google PageSpeed. While doing this experiment, I decided to choose the most popular tags used by my client and the tags that can be moved to the server container: Universal Analytics, Facebook, Bing, and Active Campaign.
GTM server container has native tags for Universal Analytics and GA4. Here you can find detailed information on how to add Universal Analytics via your GTM server container. We also created a custom template that can help you move Facebook pixel to the server environment.
Below are the results of the Google Speed Test. Google page speed showed 95 points on mobile and 100 on the desktop.
We have these tags installed on the server container: Universal Analytics, GA4, Facebook (base and conversion tracking), Hubspot, and Klaviyo tag.
When we moved pixel to the web container, Google PageSpeed results decreased to 56 points.
If you move tags to the Google Tag Manager server container, it will speed up your site. The level of its impact will depend on the tags that you are using. In this test, I tried to use the most popular tags that my clients are using: Universal Analytics, GA4, Facebook, Bing, and Active campaign. But there is also another outcome. For now, not all the pixels can be set up via the server container. For example, Twitter and LinkedIn do not support server-side tracking (hopefully, it will change soon). And tools like Hotjar are not compatible with server-side tagging by default.
All you have to do is to click Need assistance, fill up the form, and we will send you a quote.
Find out how to use server-side tracking with Google Tag Manager and avoid being blocked by AdBlocker.Apr 1, 2021
In this article, I want to show you how to use Data Tag. This custom tag sends parameters from the Google Tag Manager Web Container to the Server Container. When used together with the Data Client for the Google Tag Manager server container, it allows sending data layer variables, custom parameters, and other data from the web to the server container. As a result, Data Client retrieves information from the Data Tag into the Google Tag Manager Server Events.Feb 28, 2021
Server-side tagging has been one of the main trends in web analytics for the last couple of years. Ad blockers, Intelligent Tracking Protection, 3rd party cookie restrictions, regulations like GDPR made analytics and advertising companies start worrying about how and what information they collect about site visitors. Server-side tagging allows moving third-party tags off your site and into a cloud server. In this case, third-party pixels are loaded directly from the could server rather than your site. In this article, I will explain and demonstrate the basics of setting up Google Tag Manager server container, server Universal Analytics, GA4, and Facebook Conversion API.