DataSag guides · Updated 27 October 2026

Load analytics without blocking rendering on Vue with Vite

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 Vue with Vite.

Start with the Vue with Vite installation

Add one deferred external script to the root index.html used by the Vue Vite app. Keep it outside single-file components and preserve the application mount element and module entry. Build and publish the correct Vite application so the HTML visitors receive contains the project key.

An onMounted loader inside a route component can execute again when that component is recreated. Keep loading in the document rather than adding a new tracker through watchEffect or a route watcher. Inspect SSR-specific execution separately if your app adds server rendering.

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 Vue with Vite

  1. Keep the deferred external script in Vite index.html and preserve the Vue entry module. Avoid moving the loader to onMounted just to delay work, because route remounts can then execute it repeatedly.
  2. Build and measure the actual public app with consistent network and cache settings. Include the earliest meaningful action so a later loader cannot appear faster merely by missing measurement.
  3. Inspect route transitions separately from initial loading and confirm no watcher or component adds another tracker. A cached network resource still has execution cost if the loader runs again.

The Vue production document loads one non-blocking tracker with reactive lifecycle and early-action coverage checked 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 Vue with Vite

The shared installation belongs in the head of the Vite application root index.html. 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 Vue with Vite guides

Full Vue with Vite setup guide · Search and AI visibility

References

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