Recognised third-party embed reference in static page markup
ShipReady found a recognised third-party embed or provider reference in static executable or fetch-bearing page markup.
Why it matters
Embedded video, maps, chat, social, and similar services have their own runtime behavior. A recognised provider reference is a useful prompt to decide whether the embed is needed and to review the provider's behavior for the way your product uses it.
How ShipReady detects it
What it inspects
ShipReady reads fetch-bearing HTML attributes and executable inline script or style content for supported YouTube, Vimeo, Maps, reCAPTCHA, Disqus, Intercom, Drift, and selected social-widget signatures.
What triggers a finding
The rule triggers when one or more supported embed-provider signatures appears in the inspected static evidence. The privacy-preserving youtube-nocookie.com variant is intentionally excluded.
What the evidence shows
The evidence proves that the page contains a recognised third-party embed or provider reference in static executable or fetch-bearing markup, and names the matched provider or providers.
Limits of this check
ShipReady does not make a third-party request, execute the embed, inspect third-party response headers, or observe browser storage, cookies, IP transmission, tracking, or consent state. A provider reference does not prove that a third-party cookie was set or that a browser contacted the provider.
How to fix it
Review whether the embed is needed
Identify the component or script that introduces the reported provider and decide whether it is necessary on this page.
Review provider options
Where it fits the product, review provider-supported privacy-preserving modes or alternatives. These options vary by provider and use case.
Consider the loading design
For non-essential content, consider whether a click-to-load or other deferred loading design is appropriate for your product and user experience.
How to verify the change
Review the embed in a browser
Use a clean browser profile and network tools to inspect the actual provider requests and storage behavior for the deployed embed, including any loading conditions your product implements.
Expected: The observed provider behavior and loading design match the product's intended use.