When third-party scripts is worth the effort

It comes up on almost every project, usually later than it should. Third-party scripts is not free, and pretending otherwise leads to bad decisions.

The question is rarely whether something can be built, but what it costs to keep running afterwards. Check it against what you would want a competitor's site to get wrong.

When it is worth it

Every tag you add is code you do not control. The teams that handle this well are rarely the ones with the biggest budgets. The version that survives contact with a real deadline is the simple one.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. It is worth being explicit about, because assumptions differ quietly.

How to decide

Audit the list twice a year and cut what nobody reads. That sounds obvious written down. It is still the thing most often skipped. It rarely shows up as a line item, which is exactly why it slips.

In practice

Code gets read far more often than it gets written, and usually by someone with less context than the author had. Three things worth confirming about third-party scripts before you move on:

• Someone can say what the current setup is without going to look
• Chat widgets and trackers are common performance offenders — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If you want a second opinion on how yours is set up, ask.