Sharing, Links & Measurement

Bounce Rate

Definition

Bounce rate is a ratio: sessions with a single recorded interaction, divided by all sessions, expressed as a percentage. The classic definition, from Google Analytics before version 4, counted a session with exactly one pageview as a bounce regardless of how long the person stayed. GA4 retired the metric in favour of engagement rate, where a session counts as engaged if it lasts over ten seconds, fires a conversion, or reaches a second page — and bounce rate became simply the inverse of that. Both definitions depend on the measuring tool observing more than the arrival, which means a script in the page. An edge counter that records requests as they are served sees arrivals and nothing else, so it can report views, downloads, referrers and countries, and cannot report a bounce rate at all.

Why It Matters

A high bounce rate is treated as a verdict when it is often just a description of the content. A single-page document has nowhere else to go, so its bounce rate sits near 100 percent whether the reader loved it or closed it in disgust — the number is structurally meaningless there. Meanwhile a genuinely bad figure hides in plain sight on a multi-page site, where 85 percent on a landing page that has a form on the next step really is telling you something broke. The useful habit is to ask what the second event was supposed to be. If there is no second event by design, the metric is not available to you and a view count with a download figure will serve you better.

How It Works

The tracking script sets a session identifier, usually in a cookie or in browser storage, and records the arrival. Every subsequent pageview, click on an outbound link, or timed engagement event is attached to that identifier. When the reporting window closes, sessions carrying one event are counted as bounces. Sessions are typically cut after 30 minutes of inactivity, so a reader who leaves a tab open over lunch and returns can create two sessions and one artificial bounce. Because a static host such as 99helpers serves files without running anything on the page, the only route to a bounce figure is to add an analytics snippet to your own HTML — at which point cookie consent obligations may follow, depending on what the snippet stores.

Real-World Example

A consultant publishes a single-page proposal at northgate-proposal.99helpers.site and adds a privacy-friendly analytics snippet before sending it. The tool reports a 96 percent bounce rate, which alarms him until he realises there is exactly one page to view. He stops reporting it and looks instead at the 43 views against 9 daily uniques and the two PDF downloads of the appendix — three numbers that actually describe what happened.

Common Mistakes

  • Expecting a bounce rate from cookie-free edge counting — it measures requests, not what the visitor did after arriving
  • Judging a one-page document by its bounce rate — with no second page to reach, the figure is close to 100 percent by construction
  • Comparing bounce rates across tools — the old pageview-only definition and the GA4 engagement definition produce very different numbers for the same traffic

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →