Help center

Home Web Performance Optimisation (WPO)[WPO-004] Find third-party scripts that block the experience

Web Performance Optimisation (WPO)7 min•Difficulty: Intermedio

[WPO-004] Find third-party scripts that block the experience

Attribute waits to each external domain before removing or deferring an integration.

Ingeniería de Rendimiento AnayilUpdated: 2026-10-10

Apply this guide to your situation

This answer covers “[WPO-004] Find third-party scripts that block the experience”. Read it with the summary and confirm that the symptom and service match what you are experiencing. Available options can vary by plan and account setup.

Before changing anything, note what you expected, what happened and roughly when. Check whether the issue affects one page or the whole service.
Save the full error message and note recent changes. Hide passwords, access codes, personal data and keys before sharing screenshots or logs.
If a step requires administrator access, restarting services or editing server files, stop if you do not administer that server. Send support the service name, error and checks you have already made.

L3 technical diagnosis

Performance / configurationSeverity: Medium; high if conversion or availability is affected

User symptoms

The page remains unresponsive even though the origin has already delivered the HTML.

Observed code or message

Long tasks attributed to third parties; external `net::ERR_*` or timeout

Likely root cause

Analytics, chat, ads, maps and tag managers can add DNS, TLS, JavaScript and cascading requests. A slow vendor can block the main thread or interaction.

Likely-cause and resolution matrix

Follow a branch only when evidence supports it. A symptom may have more than one cause; do not change layers by guesswork.

01Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):

bash

Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

02Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):

bash

Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

03Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):

bash

Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

04Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):

bash

Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

05Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):

bash

Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

Prerequisites

Authorised access to the affected site, repository or service metrics.
A reproducible URL and timestamp; use staging for infrastructure changes.
A backup or rollback method for configuration and deployments.

Important warnings

Inspection commands do not authorise production changes. Do not run load tests or global purges without an approved plan.
Never store private responses in shared caches. Server changes in Anayil Panel depend on the controls available for the service and may require its administrator/provider.

Step-by-step walkthrough

1. Reproduce and narrow the issue

The page remains unresponsive even though the origin has already delivered the HTML. In DevTools Network and Performance, group by domain and identify tasks, requests and dependencies. Repeat with a cold cache and preserve the reproducing flow.

bash

# In DevTools: Network → Domain / Initiator; Performance → Long tasks
# From a terminal: curl -sS -o /dev/null -w '%{time_namelookup} %{time_connect} %{time_total}\n' https://vendor.example/

Expected output:

Long tasks attributed to third parties; external `net::ERR_*` or timeout

2. Apply the appropriate correction

Remove duplicate tags; load non-essential features on demand and use `defer` only when ordering and dependencies allow it. Agree on timeout, consent and fallback with the integration owner. Do not self-host third-party scripts without reviewing licence and update policy.

3. Verify the experience

Test the journey without each integration and then with it; confirm functionality and consent still work and blocking requests/tasks decrease.

Expected output:

The improvement is reproducible on the affected route and profile with no new functional errors.

Troubleshooting & Solutions

Long tasks attributed to third parties; external `net::ERR_*` or timeout

Root cause: Analytics, chat, ads, maps and tag managers can add DNS, TLS, JavaScript and cascading requests. A slow vendor can block the main thread or interaction.

Resolution: Remove duplicate tags; load non-essential features on demand and use `defer` only when ordering and dependencies allow it. Agree on timeout, consent and fallback with the integration owner. Do not self-host third-party scripts without reviewing licence and update policy.

Rollback and recovery plan

Roll back only the changed directive, dependency or release using the recorded value. If 5xx errors, data exposure or session failures occur, have the operator disable the new rule and retain redacted logs for analysis.

Related runbooks in this category:

[WPO-001] Separate origin latency from browser delay7 min [WPO-002] Diagnose intermittent latency without mislabeling constant slowness7 min [WPO-003] Reduce redirect chains in the page-load path7 min

Was this technical guide helpful?

Facing a production outage?

Hosting Anayil system administrators can directly intervene on your server infrastructure.

Open Support Ticket at Hosting Anayil