Start free

Worker-built script bundles

One opt-in URL that carries the core script plus only the add-ons you tick. Unused add-ons cost 0 bytes, and the core script never grows.

Getting startedFeature page: Worker-built script bundles
Worker-built script bundles: example screenshotWorker-built script bundles: example screenshot
Example screenshot with made-up data, not a real customer’s numbers.

What it does

On Manage, under the existing install tag, you can tick the add-ons a site needs. The Worker builds a single file at a new URL such as /js/script.events.forms.js. Custom events use the events script (which already includes pageviews) so the core is not added twice. The default tag, /js/script.js (845 B) and every existing add-on URL keep working exactly as they are.

Why it matters

The way to turn on extra features without making every site download every add-on, and without growing the core script.

How to use it

  1. The default install tag still loads /js/script.js only (845 B). Copy it from Manage or Your sites as before.
  2. To combine add-ons, open Manage, tick only the modules you need, and copy the bundle tag. The URL looks like /js/script.events.forms.js.
  3. Custom events use the events script, which already includes pageviews, so the core is not added twice. Existing /js/events.js and every other add-on URL keep working.

How it works

How a script bundle is built1. On Manage you tick only the add-ons this site needs, or you leave the core tag as it is. 2. Does this change /js/script.js or an existing add-on URL, or write a row? (otherwise: No: those URLs stay byte-for-byte. The bundle is a new URL, built in memory.) 3. The Worker serves /js/script.<modules>.js: core, or events.js when custom events are on, plus only the ticked add-on files. 4. Your pages load one tag. Unused add-ons cost 0 bytes, and the core script never grows.1On Manage you tick only theadd-ons this site needs, oryou leave the core tag as itis.2Does this change /js/script.jsor an existing add-on URL, orwrite a row?No: those URLsstaybyte-for-byte.The bundle is anew URL, builtin memory.3The Worker serves/js/script.<modules>.js: core,or events.js when customevents are on, plus only theticked add-on files.4Your pages load one tag.Unused add-ons cost 0 bytes,and the core script nevergrows.
From the Manage bundle builder and the Worker. The default install tag is unchanged.

Privacy

Limits

Plans

Every plan, including Free. quietstats is free during launch: the Free plan covers 1 site and 5,000 pageviews a month, and no card is needed. See pricing.

Questions

Is the core script replaced?

No. The default tag and /js/script.js stay as they are. The bundle is a new, optional URL.

Can I still use /js/events.js on its own?

Yes. Every existing add-on URL keeps working, byte-for-byte.

Does this write rows when someone downloads the bundle?

No. The Worker builds it in memory from the same files.

Related