DataSag guides · Updated 27 October 2026

Load analytics without blocking rendering on Carrd

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

Start with the Carrd installation

On a Carrd plan that supports custom code, add an Embed element and set its type to Code. Paste the tracker, choose Hidden style and Head location, then publish. Carrd's documentation currently requires Pro Standard or higher for this mechanism. Use the published URL to verify the result.

An Inline Embed appears at its position in the document; a Hidden Head Embed is the intended shared loader. Carrd sections often use fragment navigation on one document. The current DataSag tracker counts pathname changes, so section switches should not be assumed to be separate pageviews.

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 Carrd

  1. Use defer on the external tracker in the Hidden Head Code Embed. Check other hidden Embeds for copies before measuring; two installations can execute even if the browser downloads the same external file only once.
  2. Publish and measure the public site with its normal background media and widgets. Fix the viewport and network settings for before-and-after checks. The Carrd editing interface is not the page your visitors load.
  3. Test a short visit and an early click on the primary action. If custom code delays the tracker until later, record that coverage change. Fragment section navigation should not be used as evidence of another document download.

The deferred published installation is measured alongside Carrd media, with early-action coverage checked explicitly.

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 Carrd

The shared installation belongs in a Code Embed with Hidden style and Head location. 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 Carrd guides

Full Carrd setup guide · Search and AI visibility

References

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