The Performance Center enables you to monitor the size of your AB Tasty generic tag.
It displays a list of seven guidelines to follow to enhance the tag performance on your account.
⭐ Good to know
You can also check the tag’s size in the network tab of your browser by searching for the try.abtasty.com/identifier.js file.
On the top right of the screen, you can see the global performance of your AB Tasty tag:
0 improvements to go
All guidelines are respected (optional points are not taken into account).
Between 1 and 5 improvements to go
At least one guideline is not respected (optional points are not taken into account).
Each guideline displays a status, showing whether it is currently respected () or not ().
Here are the 7 points you must monitor to ensure good tag performance:
- Tag weight
- Heavy campaigns
- Targeting verification
- Old widget version
- Old campaigns running
- jQuery injection
- Global Code size
- Campaign loading
- Enablement of framework auto-reload (optional)
- Activation of Cross-Domain Tracking (optional)
✅ Guideline: tag weight should be under 125 kB.
📝Explanation: a heavy tag is mechanically slower to download and thereby may affect your website performances.
⚙️Resolution: follow the guidelines listed below.
✅ Guideline: Campaigns should not contain too much code.
📝Explanation: The more code you add in your campaigns, the bigger its size will be and the heavier the global tag will be. Also, heavy chunks of code take time to be analyzed by the browser and this may slow your website and cause a flickering effect.
We recommend not managing heavy page reformatting with AB Tasty, and avoiding inserting large files such as images or lists/tabs directly into the editor. If you need external resources, you can host them directly on your website.
⚙️Resolution: Go to each listed campaign to review and pause them or remove unused code.
✅ Guideline: Only use the regular intervals verification option when necessary.
📝Explanation: When setting up the targeting of your campaign, you can choose if you want your conditions to be verified on page load or at regular intervals until they are met. The latter option may be useful when some conditions trigger after the page loads, but has a major impact on your website performance. This feature will be deprecated at the end of the year (2021) and alternatives will be introduced beforehand. However, we recommend pausing or adapting the campaigns still using it.
⚙️Resolution: Go to each listed campaign to review and consider using the ‘when the page loads’ option if possible.
Old widget version
✅ Guideline: Certain widget versions are outdated and should no longer be used.
📝Explanation: We constantly update our widgets to make them lighter and more efficient. When keeping an old campaign live or when duplicating a campaign, you may have an old version of a widget which adds weight to your campaign and global tag.
⚙️Resolution: Go to each listed campaign to review and reupload the latest version of the widget from the widget library.
Old campaigns running
✅ Guideline: Old campaigns should no longer be running on your account.
📝Explanation: Letting a campaign run for several months is rarely best practice for the following reasons:
- The changes you made in your old campaigns may be different from what is hard-coded on your website and you may have forgotten that these campaigns are still running.
- Old campaigns are adding unnecessary weight to the AB Tasty tag.
⚙️Resolution: Hardcode the modifications of your campaign(s) on your website, pause the campaign(s) or replace them.
✅ Guideline: If you don't need jQuery, remove the jQuery injection..
📝Explanation: When using AB Tasty, you may want to create your campaigns using jQuery. To do so, you can either use your own version of jQuery already implemented on your website or use AB Tasty to inject its own version directly into the tag (approximately 40 kB). We highly recommend you don't select this last option as it will add a lot of additional weight to your tag.
⚙️Resolution: Go to your account settings and select Do not use jQuery or Use my own jQuery.
Global Code size
✅ Guideline: Global Code should not contain more than 1,000 characters.
⚙️Resolution: Go to your Global Code and remove code that is unused.
✅ Guideline: Set each individual campaign to be downloaded only once their targeting is valid (the deferred campaign feature).
📝Explanation: By default, all your live campaigns are included in the tag. You may not want all your visitors to download all the campaigns. Using the deferred campaign feature allows you to purposely delay a campaign so that it is not included in the tag. For more information, refer to Using deferred campaigns.
⚙️Resolution: For each campaign you want to defer, go to Advanced options (step 6) and select Deferred in the Tag Performance Optimisation section.
Enablement of framework auto-reload (optional)
✅ Guideline: If this feature is not needed, disable it.
📝Explanation: To handle Single Page Applications (SPA) and some other website technologies, the framework auto-reload feature is activated by default. This means the tag is looping every 100 ms to make sure your visitors haven't switched pages, which would lead to a reassessment of the targeting.
⚙️Resolution: Go to your account settings and select Enable the automatic reload of the framework > No.
Activation of Cross-Domain Tracking (optional)
✅ Guideline: When not running your tag on several domains, disable this feature.
📝Explanation: Cross-domain tracking can be useful if you are running the AB Tasty tag on several domains (not including subdomains), but having this feature enabled means adding an additional piece of code into your tag.
⚙️Resolution: Go to your account settings and delete Cross-domain tracking if not needed.
Need additional information?
Submit your request at email@example.com
Always happy to help!