DataSag guides · Updated 27 October 2026

Load analytics without blocking rendering on Remix v2

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 Remix v2.

Start with the Remix v2 installation

For a Remix v2 application, add one deferred external script to the existing document head in app/root.tsx. Preserve Meta, Links, Outlet, ScrollRestoration and Scripts in their established locations. Keep the tracker outside nested route components. This guide targets Remix v2 conventions; inspect different framework versions before copying their root shape.

An action or loader runs on the server and cannot use the browser window. Root error handling can render a different document. Test direct entries, client navigation and your relevant error route without adding another script to every nested route.

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 Remix v2

  1. Keep the deferred tracker once in the Remix root head, preserving framework Scripts and ScrollRestoration. A nested route effect is not an equivalent global loading mechanism.
  2. Measure the production build through its deployed adapter on a direct nested entry. Compare the same route and cache conditions before and after, including when the first useful form interaction can occur.
  3. Measure client Link transitions separately from document loading. Inspect whether the root persists without another execution. If you experiment with later loading, test progressively enhanced forms that can be submitted before that loader is available.

The Remix root loads one tracker non-blockingly with direct-entry and progressive-enhancement coverage documented separately.

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 Remix v2

The shared installation belongs in the head of the existing document in app/root.tsx. 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 Remix v2 guides

Full Remix v2 setup guide · Search and AI visibility

References

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