Group
  • Performance

    Audit what my third-party scripts are costing me

    Measure the performance and privacy cost of every external script and cut the ones that don't earn their keep.

    • Improve quality
    • Plan & validate
    • Beginner
    • General

Free Prompt

My pages load third-party scripts (analytics, chat widgets, tag managers, social embeds, A/B tools) and I suspect they're costing more than they're worth. Inventory every external script my pages load. For each one, report: 1. What it is and what business purpose it supposedly serves. 2. Its cost: transfer size, whether it blocks rendering, whether it spawns additional requests (tag managers loading more tags), and its impact on total load time. Measure with a real tool if possible. 3. Where it loads: every page, or only pages that need it. Then produce a recommendation per script: 1. Keep: it earns its cost. Note any loading improvements (async, deferred, load on interaction). 2. Restrict: it's only needed on certain pages (a chat widget on the support page, not the landing page). Scope it. 3. Defer to interaction: load it when the user signals intent (click to open chat, scroll to the video) instead of on page load. 4. Remove: it was an experiment, a leftover, or its value doesn't justify the weight. Name these plainly and let me decide. Don't remove anything without my confirmation. The deliverable is the audit and recommendations, then I'll pick. Also note any script that sets cookies or sends user data off-site, since those belong in my privacy policy whether or not I keep them.

What This Does / How This Helps

This inventories your third-party scripts, measures what each costs in load time and behavior, and recommends keep, restrict, defer, or remove for each. Third-party scripts accumulate like barnacles: an analytics experiment here, a chat widget there, a tag manager loading tags nobody remembers. Each one adds weight, main-thread work, and another company touching your users' data. On a vibe-coded landing page they're frequently half the total page weight. The audit forces each one to justify itself, and the per-page scoping fix alone usually recovers noticeable speed.

Want to skip doing this by hand?

Fortivibe audits your app for all of the areas these prompts cover (and more).

See What We Check

Related Prompts