DataSag guides · Updated 27 October 2026

Load analytics without blocking rendering on Express with EJS

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 Express with EJS.

Start with the Express with EJS installation

Add the deferred tracker to the shared EJS partial that emits your document head. Include that partial through the existing local include pattern in each intended template. EJS has no built-in universal layout convention, so identify your actual application composition rather than assuming a views/layout.ejs file exists.

A res.send response or a separately rendered error template can bypass your usual partials. Keep the snippet in browser HTML rather than Express middleware that only logs requests. Never include a template path supplied directly by an untrusted visitor.

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 Express with EJS

  1. Add defer to the external tracker in the shared EJS head include. Preserve the existing wrapper and browser bundle tags rather than introducing another script through Express response middleware.
  2. Measure the published rendered route with fixed network and cache settings. Include a route using another wrapper so a missing partial does not create an artificially fast comparison.
  3. Compare the first intended browser action with tracker availability. Keep Node response timing separate from browser parsing and execution, and verify custom client-side partial updates do not repeat the global installation.

The rendered EJS documents use one non-blocking tracker with browser and Node response costs assessed 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 Express with EJS

The shared installation belongs in a shared EJS head partial included by the intended page templates. 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 Express with EJS guides

Full Express with EJS setup guide · Search and AI visibility

References

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