Skip to content
Raptor home
Menu

Third-party JavaScript

javascript.js_third_party_heavy
Priority
Low
Severity
Warning

What we look for

These pages load more than 10 scripts from servers other than the page's own, such as analytics, ads, chat and tag managers.

Why it matters

Each outside script adds requests to servers you do not control, which slows the page and can share visitor data with the companies behind them.

How to fix

Remove tags and widgets you no longer use, in your tag manager, CMS or page template. Load the rest after the main content, or only on the pages that need them.

What it cannot know

Scripts from your own subdomains, such as cdn.example.com, count as outside scripts here.

Seen in a real crawl

From a crawl of the js-heavy fixture, a test site from Raptor’s fixture suite.

Low

1 page loads many scripts from other companies

  • /many-scripts/12 third-party script(s) from cdn0.example.com, cdn1.example.com, cdn2.example.com, cdn3.example.com, cdn4.example.com, cdn5.example.com, cdn0.example.net, cdn1.example.net, cdn2.example.net, cdn3.example.net (+2 more)
Paths on http://127.0.0.1:8004raptor 0.3.0, 17 Oct 2026

Open this finding in that crawl’s report

Where you’ll see it

The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.

Terminal
When it is one of the five findings under Fix first, raptor crawl prints the id under it.
Check: javascript.js_third_party_heavy
crawl.json and the CSV
The crawl JSON names the finding by this id, and so do the CSV and raptor_query.
"check_id": "javascript.js_third_party_heavy"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=javascript.js_third_party_heavy
MCP
raptor_findings with this check_id returns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.
raptor_findings {
  "job_id": "...",
  "check_id": "javascript.js_third_party_heavy"
}