Introduction

Lynq

Lynq is web analytics that respects your visitors. One script tag, no cookies, no consent banner, and a dashboard that answers the questions you actually have: who came, from where, what they read, and whether they did the thing you built the page for.

What you get

  • Overview with unique visitors, sessions, pageviews, bounce rate, engaged time and your KPI, compared with the previous period; the trend on this weekday’s usual range, three highlights computed from the numbers (the unusual day and the note on it, the mover, the KPI’s pace), when people come by hour and weekday, and what moved since the previous period.
  • Pages, Sources, Audience as ranked tables; any row becomes a filter with one click. Pages opens on how sessions move through the site, where they start and where they end, and a selected page shows what came before and after it, with how far down it was read. Audience is who the visitors are: when each country is awake, viewport widths against your breakpoints, browsers by operating system, and the ledgers of countries, regions, cities, languages, browsers and systems.
  • Attention: which pages hold your visitors’ time, how far they read, and which ones help them convert.
  • Bots: which AI assistants and crawlers read your site, and whether they came to answer someone or to train a model. A few lines on your server; the browser never sees a crawler.
  • Notes: a dated sentence pinned to the site, drawn on the charts where it happened, so a spike reads “Launched on Product Hunt” instead of a mystery. A deploy pipeline can add one through the API.
  • Journeys: any converting session or any session on a page opens as a timeline, every page and event in order, so “what did they actually do” has an answer.
  • Events and goals: custom events with properties, goals on a page or an event, conversion and revenue.
  • Funnels: name the steps of a flow, in order, and see where people stop.
  • Experiments, A/B tests: one call splits visitors between variants and keeps them there; each test reads against any goal, with checks that say when a result cannot be trusted and arithmetic you can read as often as you like.
  • Health: Core Web Vitals per page with the element responsible; when turned on, uptime checks with incidents, and JavaScript errors grouped with the sessions they hit.
  • Accessibility: measured on real visits, when turned on: how many were navigated by keyboard, at 200% zoom or with reduced motion requested, what got in the way (focus that could not leave a dialog, a clickable card no keyboard reaches, a page that scrolls sideways) and what it cost against your goal. Aggregates over at least 20 sessions, related to WCAG 2.2 criteria, never a score; screen readers cannot be detected and are not counted.
  • Realtime: who is on the site right now and what they are looking at.
  • For agents: Claude Code, Cursor and Codex connect over MCP with one key and ask the same questions as tools, each answered with a sentence and the numbers behind it.
  • Links that carry the view: the range, the filters and the table view are in the address bar, so a link shows a colleague exactly what you see.

Install in one line

<script defer src="https://lynq.byharsh.com/js/lynq.js" data-site="your-site.com" data-vitals></script>

That is the whole install. Add your site, paste the line, and Lynq confirms the first pageview as it lands.

How it stays private

The script keeps nothing in the browser but a per-tab session record. A visitor is a number computed on the server from the request and a salt that changes every day, so the same person is a different number tomorrow and cannot be followed across days. Global Privacy Control is always honoured. Read the whole list; it is short.

See it in action

A real site with a year of traffic is one click away: choose See Lynq in action on the login page. No account needed, and Lynq is always free.

Add the snippet