DataSag guides · Updated 27 October 2026

Load analytics without blocking rendering on Ghost

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

Start with the Ghost installation

Add the DataSag script to the site-wide Site Header area of Ghost Code Injection. Replace the example public key, save the change and open the public publication. Keep the active theme's ghost_head helper because that helper outputs header injection. This does not require a DataSag-specific Ghost integration.

Ghost also offers code injection for individual posts. A post-level snippet does not cover the publication, and a theme-level copy can duplicate a global injection. Test a published article and a standalone page outside Ghost Admin.

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 Ghost

  1. Keep the external script deferred in the publication-wide header injection. Compare it with theme assets and post-level snippets before testing so the page does not execute multiple installations under different loading conditions.
  2. Measure a published article containing typical images and embeds using fixed network and cache settings. Inspect tracker timing alongside theme assets; an editor preview includes different resources and is not a useful public-page baseline.
  3. Repeat the check on a short article where visitors might leave early. If you experiment with a later custom loader, record which early interactions it misses rather than treating reduced request activity as an unqualified improvement.

Public-theme loading measurements cover representative content and record measurement coverage alongside timing changes.

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 Ghost

The shared installation belongs in the site-wide Site Header code injection field. 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 Ghost guides

Full Ghost setup guide · Search and AI visibility

References

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