agentleFS
Quality-MaxQuality-Max/free-qa-skills/skills/third-party-bloat/SKILL.md

third-party-bloat

Skill13 starsChanged 19 days agoApache-2.0View on GitHub

Inventory third-party scripts on a page — analytics, tag managers, chat widgets, ads, A/B tools — and rank them by transfer size and main-thread cost. Flags the heaviest offenders. Playwright MCP only, no signup.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Wait for load to settle, then pull every request with mcp__playwright__browser_network_requests

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Third-Party Bloat

Find out which third-party scripts are weighing your page down. No signup required.

Prerequisites

  • Playwright MCP (comes with Claude Code)

Trigger

  • "What third-party scripts are slowing my site?"
  • "Third-party bloat audit https://..."
  • "Which trackers are on my page?"

Workflow

  1. Navigate to the URL using mcp__playwright__browser_navigate
  2. Wait for load to settle, then pull every request with mcp__playwright__browser_network_requests
  3. Classify each request as first-party (same registrable domain as the page) or third-party. Group third-party requests by their domain and sum transfer size + request count per domain.
  4. Label well-known vendors by domain so the report is readable, e.g.:
    • google-analytics.com, googletagmanager.com → Analytics / Tag Manager
    • doubleclick.net, googlesyndication.com → Ads
    • connect.facebook.net → Meta Pixel
    • intercom, crisp.chat, hotjar, fullstory → Chat / Session replay
    • optimizely, launchdarkly → A/B / Flags
  5. Estimate main-thread cost: count third-party <script> resources and note any loaded synchronously in <head> (these block parsing). Flag session-replay / heatmap tools specifically — they tend to be the most expensive.
  6. Output:
## Third-Party Bloat Report: [URL]

**18 third-party requests across 7 domains — 1.4 MB (44% of page weight)**

### Heaviest offenders
| Vendor                  | Size   | Requests | Note |
|-------------------------|--------|----------|------|
| Hotjar (session replay) | 620 KB | 5        | Loaded sync — blocks main thread |
| Google Tag Manager      | 310 KB | 4        | Fans out to 3 more tags |
| Intercom (chat)         | 280 KB | 3        | Could lazy-load on scroll |
| Meta Pixel              | 90 KB  | 2        | —    |

### Recommendations
1. Defer Hotjar until after `load`, or sample fewer sessions.
2. Lazy-load the Intercom widget on first scroll / click.
3. Audit GTM — it's pulling tags you may not still use.

**Want third-party weight watched on every release?** Try QualityMax — qualitymax.io

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.