Technote

Performance optimization Practical

Series Speed and conversion Part 5 of 8

Who pays for the milliseconds a tag adds?

A tracking script does not stop at downloading. While it is parsed and executed the main thread is busy, and a busy page ignores fingers. That cost is measurable.

Adding a tag in a tag manager takes under a minute. No approval, no deployment, and on screen it is one more row in a list. Addition being that cheap while the cost stays invisible is the whole shape of this problem.

What one script goes through

The stages one third-party script passes through — the last two freeze the screen

A third-party script comes from another domain, so the browser must first resolve it and negotiate a secure connection, then fetch the file. Up to here it is a question of file size and connection quality.

What follows matters more. The browser has to parse and execute that JavaScript, and it does so on the main thread — the same thread that paints the screen and answers taps. While a script occupies it, the page sits in the state where it is visible but does not respond to touch. Visitors do not file that under “slow”; they file it under “broken”.

Many tags also load further scripts of their own. You added one line and several files arrive, which is why the tag manager’s list cannot tell you the real load.

Easy to add, hard to see

Each addition is small; the burden always arrives as a total

That last line is a particular trap. Development and staging environments usually carry no marketing tags, so the page a developer sees and the page a customer sees are different pages. “It is fast on our side” is not dishonesty — it is a different screen.

Measuring the cost yourself

Rather than quoting how much this costs, find out how much it costs you. The procedure is short.

Measure the landing page URL three times on a fixed device profile and take the median. Then use your browser’s request-blocking feature to block that script’s domain and measure three more times under identical conditions. The difference between the two medians is what that tag costs — on your site, under your conditions.

With a number in hand there are three options: remove it (tags from finished campaigns), defer it (load after first paint, or on interaction), or keep it knowing the price. The third is a legitimate choice — the point is to convert a cost you were paying unknowingly into one you are paying deliberately.

There is something to check with yourself among our free tools, and clearing tags alongside caching and server configuration is handled as one job in the optimization program.

Next part

With a lighter page, somebody now has to actually do something on it. The next part is forms — and how each individual field earns its place.

More on this topic

All technotes

Performance optimization Practical

The object cache: what Redis actually removes

Repeated identical lookups disappear. One slow query does not. Miss that distinction and you will wire up Redis and then ask why nothing got faster.

Developers 7 min read

Performance optimization Practical

This is how a landing page gets heavy

Nobody decides to make a landing page heavy. It accumulates: one addition per campaign, and nothing ever removed when the campaign ends.

Marketers 6 min read

Performance optimization Practical

The N+1 problem: get_post_meta in a loop, and priming

WP_Query primes caches for its own results only. A hand-built list of IDs gets none of that for free — and that difference decides your query count.

Developers 7 min read

₩270,000 · Join the program