DataSag guides · Updated 27 October 2026

Load analytics without blocking rendering on Squarespace

Use the platform's non-blocking external script mechanism and install the tracker once. Measure the published page before and after the change; script size alone cannot predict the effect on your website. This guide applies to Squarespace.

Start with the Squarespace installation

Open the site-wide Code Injection settings and paste the tracker into Header. Save the change, then open the public site outside the editor. Code injection availability depends on your plan; consult the platform documentation for your account.

A page header field or a code block may also contain the tracker. A code block only covers its page and can be removed with the content. Site-wide injection is easier to audit.

Use the public project key from the DataSag project you are inspecting. A test on a preview domain does not confirm that the production domain has the same code or settings.

Load analytics without blocking rendering in Squarespace

  1. Use a deferred external script through site-wide Header injection. Check page code blocks before testing so you do not compare a single installation against a page that executes the tracker twice.
  2. Measure the actual public website with fixed throttling and cache conditions. The editor includes different scripts and interactions, so its timing is not a useful customer-facing performance baseline.
  3. Check a normal page and content entry, then test the first intended action. If another custom-code mechanism delays tracking, compare action coverage as well as load timing before keeping that change.

Public Squarespace output uses one non-blocking installation and the comparison reflects customer pages rather than editor behavior.

Complete the collection checks

  1. Record a baseline of the published page using the same browser, device emulation and network settings you will use for comparison. Include a representative content page, not only the homepage.
  2. Use defer for a normal external HTML script, or the framework-specific loading strategy shown in the installation example. Do not add a parser-blocking synchronous script as a shortcut.
  3. Keep one installation in the shared document or layout. Duplicate execution adds work even if the browser reuses the downloaded file.
  4. Inspect the Network waterfall for tracker.js and /api/track. Compare transfer size, timing and request count on a cold load and a cached load.
  5. Check that measurement still starts at the intended point. Loading only after idle or interaction can omit short visits and early clicks; performance and coverage must be evaluated together.
  6. Repeat the measurements and record variability. Report measured results for your page rather than claiming a universal speed improvement or zero performance cost.
// Browser Console, after loading the published page:
performance.getEntriesByType('resource')
  .filter(entry => entry.name.includes('/tracker.js'))
  .map(entry => ({ url: entry.name, durationMs: entry.duration }));
// Cross-origin transfer details may be unavailable.

What a successful check looks like

The script uses a non-blocking loading mechanism, appears once and records the intended visits. Any performance claim comes from repeatable measurements of the actual site.

Record the public path you tested, the browser state, the approximate time and the observed request. Check one direct page load and one later navigation so the result covers more than the homepage.

Common mistake

A faster lab result does not prove every visitor has a faster experience. Avoid mixing a warm-cache result with a cold-load baseline.

Installation snippet for Squarespace

The shared installation belongs in site-wide Header code injection. Use this as the installation reference while checking the procedure above.

<script defer src="https://www.datasag.com/tracker.js" data-datasag-key="YOUR_PUBLIC_KEY"></script>

Related Squarespace guides

Full Squarespace setup guide · Search and AI visibility

References

Official Squarespace documentation covers the integration point. For DataSag data handling, read the privacy policy. Use support if a request fails after these checks.