Reading bounce rate three ways
By Lee Johnson ·
Bounce rate in quietstats is simple: visits that saw exactly one page ÷ all visits. A ten-minute read of one article still counts as a bounce. That is why one site-wide number rarely tells you much. Read it in these three ways instead.
1. By landing page
Open Entry pages and sort by visits. A blog post with a high bounce rate may be doing its job: the reader got the answer. A pricing or product page with a high bounce rate is a different story. Compare similar pages with each other, not with the site average.
Click any row to filter the whole dashboard to visits that started there.
2. By source
Filter by channel or source. If one source has a much higher bounce rate than the rest, its visitors are arriving with a different expectation from the page they land on. Check the link, the advert text or the post that sent them. If you tag links with UTM tags, you can compare individual campaigns.
3. By device
Filter Device = Mobile, then Desktop. A page that bounces far more on phones than on laptops often has a layout or speed problem on small screens. The optional Core Web Vitals add-on shows real loading times on those pages.
When a high bounce rate is fine
- Single-page sites and landing pages with one action.
- Articles and answers, where one page is the whole job. Use engaged time to see whether people read.
- Contact pages where the visitor phones you instead of clicking.
GA4 defines bounce rate differently (sessions that were not “engaged”), so the two numbers won’t match. See the glossary entry for a worked example.