third-party-impact

Measure third-party script impact by categorizing loaded scripts by vendor type and attributing main-thread blocking through Long Tasks. This produces a structured report with per-domain details and render-blocking resources to guide optimization.

Quantify main-thread blocking from third-party scripts using Long Task attribution. The analysis identifies script sources, measures their blocking contributions, and generates a breakdown by category and domain.

Yes, you can categorize third-party scripts into vendor types including analytics, ads, social, tag managers, CDN libraries, fonts, and video. This categorization forms the basis of the structured impact report.

The best way to identify render-blocking third-party resources is to run an analysis that detects them and estimates domain connection overhead. The resulting report highlights these resources alongside total blocking times.

Yes, this third-party impact analysis works with Playwright to automate the assessment of web vitals. It executes on the target page to generate a complete report without requiring additional dependencies.

Third-party scripts cause long tasks on the main thread when their execution blocks rendering. The analysis attributes these long tasks to specific script sources and vendor categories to pinpoint the exact overhead.