Third-Party Scripts and Embeds

The category “culprit” that surprises small business owners the most.

You install a chat widget here, a pop-up tool there, and a social feed block somewhere else, and over time you’ve created a performance problem without realizing it.

The most common third-party additions that will hurt your site:

  • Live chat widgets (Intercom, Drift, Tidio)

  • Behavior analytics tools (Hotjar, FullStory)

  • Live social feed embeds

  • Pop-up and email capture tools

  • Tag managers loaded with excessive triggers

Each one adds JavaScript to the browser’s main thread and creates additional network requests.

The result is a delay in when the page’s largest visible element loads (LCP) and a sluggish response to taps and clicks (INP). These aren’t theoretical effects; they show up clearly in performance audits and are a key reason Squarespace includes a script audit in its page speed recommendations.

Ask yourself honestly: is this script producing measurable value, or was it just installed and then forgotten?

What to do with scripts you can’t remove

For tools your business genuinely needs, a booking widget or Google Analytics, for example, you still have options. Move custom code from Header Injection to Footer Injection to reduce render-blocking impact. Use async or defer attributes when adding custom scripts via code injection.

woman writing the words Third Party on clear glass
woman writing the words Third Party on clear glass

For live social feed embeds, consider replacing them with a lightweight static alternative: a clean screenshot of your Instagram grid, linked to your profile, often performs better visually and loads in a fraction of the time.

Previous
Previous

Image Size & Format

Next
Next

Fonts