In this guide
- A server container removes vendor scripts from the browser only if you remove the browser-side tags. Adding a server tag next to the old ones adds a request.
- Typical gains are in script weight, main-thread time and INP, not in a dramatic LCP jump.
- Measure with Core Web Vitals and real-user data before and after. Do not guess.
Page speed is a real reason to try server-side tagging, and an easy one to oversell. A web container still loads on the page, and a lot of what makes pages slow (images, fonts, your theme) has nothing to do with tags. This page explains where server-side helps, where it does not, and how to measure. For what the container does, see what server-side tracking is.
How tags slow a page
- Download. Each vendor script is a file to fetch.
- Execution. Scripts run on the main thread and block clicks and scrolling.
- Network requests. Each tag sends its own request, often to a different domain.
- Layout shifts. Some widgets inject content late.
Brands that grow on cleaner data
Stores and agencies use Open Tracked to see which ads earn the sale.
Where server-side tagging helps
Fewer scripts
Instead of Meta, TikTok, Pinterest and others each loading a script, the browser sends one request to your server and the server calls the vendors.
Less main-thread work
Less JavaScript runs on the visitor's phone, which helps INP, the responsiveness metric.
Fewer connections
One connection to your own domain replaces many to different vendors.
A cached, nearby loader
Serving the container script from your own domain with the Custom Loader (all plans) can make it cache-friendly.
Where it does not help
- Large images, slow hosting and heavy themes.
- Tags that must stay in the browser, such as some chat widgets and A/B testing scripts.
- A site where the old scripts are left in place next to the server tags.
Ask Ari instead of digging through reports
Ari reads your tracking and ad data and answers in plain words.
Measure before and after
Record a baseline
Core Web Vitals in Search Console, PageSpeed Insights and your own real-user data.
Take a lab test
Run Lighthouse on a product page and the home page, several times.
Make the change
Move tags to the server and remove the browser-side copies.
Wait for field data
Real-user metrics need about 28 days to settle.
Compare
Script weight, total blocking time, INP and LCP.
What to expect
| Metric | Likely effect of removing several browser tags |
|---|---|
| Script weight (KB) | Down, often noticeably |
| Total blocking time and INP | Down if the scripts were heavy |
| LCP | Small change, unless tags delayed rendering |
| CLS | Little change |
Results vary widely. A store with ten tags can see a clear change, a store with two will not.
A realistic example
A store has ten tags in its web container: GA4, Google Ads, Meta, TikTok, Pinterest, Snapchat, a review widget, a heat-map, an affiliate pixel and a retargeting script. It moves GA4, Meta, TikTok, Pinterest and Snapchat to the server, and keeps the others in the browser. The page now loads one request to the tagging domain where it used to load five vendor scripts and send five sets of requests. Total blocking time falls and the interaction metric improves on mid-range phones. The home page score moves a few points in Lighthouse. These are typical directions, not guaranteed numbers.
The lesson is that the gain depends on how many heavy scripts you can remove. Count them before you promise anything to a client. If the answer is two or three light tags, the speed effect will be small and the reason to move is data quality, not speed.
Terms you will see
- Core Web Vitals
- Google's page experience metrics: loading, interactivity and visual stability.
- INP
- Interaction to Next Paint, the responsiveness metric.
- LCP
- Largest Contentful Paint, how quickly the main content appears.
- Total blocking time
- How long scripts keep the page from responding during load.
- Field data
- Measurements from real visitors, as opposed to a lab test.
If you want a quick sanity check, open the Network tab on a product page before and after the change and sort by size. Count the requests to vendor domains and the kilobytes they transfer. If both numbers fell clearly, the page has less to do. If they barely moved, the old tags are still there, and the next step is to find them in the web container and remove the ones the server now replaces. This takes ten minutes and is more reliable than a speed score that changes from one run to the next.
Raw events in. Clean events out.
Open Tracked collects each event on your own domain, removes the noise and sends what is left to Meta, Google Ads, TikTok.
Frequently asked questions
Does server-side tagging make my site faster?
It can, if you remove the browser-side scripts it replaces. Gains are usually modest.
Which metric improves most?
Responsiveness (INP) and total blocking time, because less JavaScript runs on the page.
Will my LCP improve?
Only slightly, unless tags were delaying rendering.
Do I still need the web container?
Yes. It sends events to your server. It becomes lighter when vendor tags move out of it.
How do I measure the change?
Compare Core Web Vitals and script weight before and after, using field data over about 28 days.
Do I need spreadsheets to read my results?
No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.
Is Open Tracked different from Open Track or Open Space Track?
No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.
Fix your tracking at the source
Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.
The Open Tracked team
We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?
Comments
Loading comments...
Guides · 6 min read
