Why are third-party scripts slowing my site? on Squarespace

Third-party scripts (analytics, ads, chat, social) often add significant weight and delay.

• Scripts loaded synchronously in the head Too many third-party scripts Heavy analytics
• Use Lighthouse or PageSpeed to see third-party impact Check Network tab for
• Load third-party scripts async or defer Use tag manager to load after

Third-party scripts (analytics, ads, chat, social) often add significant weight and delay. They can block rendering or run long tasks and hurt Core Web Vitals. Loading them asynchronously, deferring until after load, or replacing with lighter alternatives can improve speed and rankings. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not…

Scripts loaded synchronously in the head. Too many third-party scripts. Heavy analytics or tag managers. Ads loading early and blocking. Chat or widget scripts run on every page. No lazy-load or defer.

Common examples

A real-world example: after a site update, a business saw visibility drop for "Third-party scripts". They checked Search Console, found the blocking issue, fixed it, and regained impressions over the following crawl cycles.

How to diagnose

Use Lighthouse or PageSpeed to see third-party impact. Check Network tab for script size and load order. Identify which scripts are critical. Measure Total Blocking Time and LCP with/without third parties.

Recommended fixes

Load third-party scripts async or defer. Use tag manager to load after user interaction or after LCP. Replace or remove non-essential scripts. Consider server-side or proxy for analytics. Re-test performance. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task.