JENTIS is an innovative, powerful and compliant server-side tracking solution. Some benefits of server-side tracking even have a direct impact on faster page load times. Let’s start with the biggest optimization lever:
Eliminate resources that block rendering.
The following graphic should clarify the problem:
How JENTIS helps
JENTIS provides its own tag manager – the JENTIS Tag Manager (JTM) – with the advantage that it ONLY performs basic communication in the client’s browser – asynchronously, of course.
This is where JENTIS comes in:
The loading process explained briefly
A positive side effect of JENTIS: significantly higher data quality! Another advantage of fast-loading code on the client side is that data discrepancies between actual and tracked visitor numbers and sales can be reduced. Keyword: ad-blocker and tracking prevention methods (IT/ETP/TP).
This means that the marketing team has a much more reliable overview of user behavior and conversions. This in turn simplifies budget control and delivers even more effective campaigns.
But Google demands even more:
Third-party codes actually affect the landing speed of websites tremendously. Google further recommends in PageSpeed Insights:
Redundant third-party tags?
You probably have them too.
For example, you use Google Ads and Facebook and want to record your sales as conversions. To do this, you configure a Google Ads conversion tag and a Facebook conversion tag – in other words, two tags that track the same thing, namely the sale, the transaction.
From Google’s point of view: double tracking.
In addition, traditional client-side tracking will again load the library from the vendor, which in turn uses the CPU and RAM from the visitor’s computer to generate streams that are sent over the visitor’s network.
How does it work better?
Numbers, data, facts
Not in all cases. It depends on the Internet connection:
- 2G GPRS with max. 56kBit/s bandwidth: 82 seconds
- 2G EDGE with max. 220kBit/s bandwidth: 22 seconds
- 3G EDGE, UMTS: up to 13 seconds
- 3G HSDPA: 0.7 seconds
- 4G LTE: 0.24 seconds
The following graphic gives a better overview again:
So even in 4G, JENTIS can be the icing on the cake, because every improved millisecond has a positive impact on conversion rates and customer satisfaction, and thus on Google rankings. How are the 604kb calculated? We tested this with our customers.
In this case, with a large online store that is mainly active in the D-A-CH region and has switched from Google Tag Manager to JENTIS. For a while, both tracking systems were running in parallel and we took this as an opportunity for our testing.
In total, the GTM accounted for 365kb. Additional third party scripts added another 281kb to the user’s browser load. TOTAL: 646kb
In comparison, the JENTIS library loads at 42kb. This makes an advantage of 604kb over the Google solution.
You can see the details in the following graphic:
Conclusion: Optimize pagespeed with JENTIS and profit
With the Core Web Vitals, Google has given webmasters, web developers and SEOs three KPIs that have several advantages: They are clearly communicated, apply to everyone in the same way and can therefore can be optimized in a targeted and comprehensible way. SEO is thus no longer a black box. An excellent Speed Score is therefore relevant for ALL websites – for highly competitive companies it is even fundamentally important, as a fast loading time leads to an even better user experience and thus to more conversions.
However, costs and benefits must ALWAYS be put into perspective. With JENTIS, and thus with a performance-oriented and at the same time powerful server-side tracking solution, you can reduce your Pagespeed by up to 82 (!) seconds. It’s the greatest possible leverage with comparatively low resource requirements and at the same time manageable costs, because you can start using JENTIS today for as little as €500 per month.
Ready to speed up your website and boost sales? Let’s talk