DataSag guides · Updated 27 October 2026

Load analytics without blocking rendering on Angular

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

Start with the Angular installation

Inspect the Angular workspace project configuration to identify its index document, commonly src/index.html. Add the deferred external script once to the existing head and preserve the root element and build-managed assets. Build the intended application project and inspect its deployed output rather than a library package.

A workspace can contain several applications with different index files and build targets. Component templates and services should not repeatedly insert the global loader. For server rendering, keep browser API calls out of server execution.

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 Angular

  1. Use the deferred external script in the application index selected by the Angular build target. Preserve the root mount element and build-managed scripts, and remove a redundant component loader before comparing timings.
  2. Measure the published target with fixed cache and network conditions. Inspect the first intended interaction relative to tracker availability rather than using development bootstrap timing as the final result.
  3. Navigate with the Router and inspect whether a service or component reinserts the tracker. Separate a full-document baseline from later client navigation, and document hash-router coverage independently where that routing strategy is used.

The intended Angular build uses one non-blocking host script with first-action and routing coverage measured 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 Angular

The shared installation belongs in the head of the application index document selected by the build configuration. 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 Angular guides

Full Angular setup guide · Search and AI visibility

References

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