DataSag guides · Updated 27 October 2026

Load analytics without blocking rendering on Framer

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 Framer.

Start with the Framer installation

Add the tracker to the site custom code area with placement in head and scope covering the pages you want to measure. Choose the Once execution option for the tracker, rather than Run on every page visit. Publish and inspect the actual public site.

An embed or code component can run in a different document from the site. Avoid placing your only tracker inside a sandboxed embed. Route-level repeat execution can create duplicate installations.

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 Framer

  1. Keep the external script deferred in the Custom Code head entry and choose Once. Review page scope and duplicate component-based loaders before measuring a loading change.
  2. Measure the published public page with consistent network and cache settings, outside the design canvas. Include the first action you want measured because changing when custom code executes can change which early actions are observed.
  3. Navigate to another page and return while inspecting execution and requests. Avoid Run on every page visit as a performance workaround; repeated initialization can add work even when the script download is cached.

The actual Framer output loads one tracker without repeated initialization, with first-action coverage included in the timing comparison.

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 Framer

The shared installation belongs in site settings custom code for the head. 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 Framer guides

Full Framer setup guide · Search and AI visibility

References

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