Pages reference scripts from many other sites
In the reportDeclared third-party script origins exceed the configured threshold
third_party_script_origin_count · Review item
This appears when a page's HTML declares scripts from more other sites than the limit, 10 origins by default. Each outside server needs its own connection, and many requests to many servers slow a page down. Remove tags you no longer use.
Severity: Notice. The count is a prompt to review, not a measured slowdown.
Why it matters
web.dev's article on third-party JavaScript performance says setting up connections takes time and that sending too many requests to multiple servers causes slowdowns, and advises routinely auditing and removing redundant third-party scripts.
What to do
- Look at the finding: it lists the outside origins, with the scripts from each.
- Remove tags you no longer use, and do not run two tools for the same job, such as two analytics services.
- Load heavy embeds, such as chat or video, only when a visitor asks for them.
When to leave it as it is: if every script is needed and the page responds quickly, you can leave it.
What we read
We read the <script src> tags in each crawled page's HTML as served, resolved against a <base href>, without fetching or running them, so scripts added at runtime, for example by a tag manager, are not seen.
A page is reported when its scripts come from more distinct origins — scheme, host and port — outside your own domain than the limit, 10 by default; subdomains of your domain count as your own. The limit is an audit setting, recorded with each audit.
Pages that did not answer 200 with HTML are left out. A page is marked as not checked when its HTML could not be read in full or a script address cannot be resolved.
Example & evidence
Illustrative example — one page's scripts, not a live audit.
https://bakery.example/ declares scripts from 12 other origins, including:
<script src="https://widgets.chat.example/loader.js"></script>
<script src="https://stats.example/tag.js"></script>
<script src="https://cdn.reviews.example/badge.js"></script>12 origins is more than the default limit of 10, so the page is reported with every origin and its scripts.
A possible correction: remove a review badge that is no longer shown, and load the chat only when a visitor opens it.
Confirm & check again
Check for yourself: view the page source and list the different domains in its <script src> tags.
Check again: Full audit — run a new audit of the site. The finding closes when the page is crawled again, read in full, and its outside script origins are within the limit. A higher limit in your audit settings also stops the finding; the finding records the limit it used.
Limits & sources
Only scripts declared in the HTML are counted, so the real number can be higher. One company with two hosts counts twice, and no script's cost is measured.
Confidence: Medium because the count comes from the HTML as served, which tag managers add to after loading.
Sources
- web.dev, Third-party JavaScript performance — says setting up connections takes time and sending too many requests to multiple servers causes slowdowns, and advises routinely auditing and removing redundant third-party scripts. Checked 29 September 2026.
Editorial review: 29 September 2026