--- title: "High Bounce Rate: When It Is Not a Problem" description: "High bounce rate is often fine: what a bounce means in Universal Analytics, the page types where it is normal, and the numbers to read beside it." canonical: "https://socialinfluencebuilder.com/en/blog/high-bounce-rate-analytics/" lastmod: "2016-12-12T18:24:00+00:00" lang: "en-CA" format: "markdown" --- HTML version: # High Bounce Rate: When It Is Not a Problem > **Archive note.** This article describes the situation as it stood when it was published. The rules, tools and features it mentions may have changed since. Check the current information with the official source before acting. High bounce rate: it is not a problem when a single page gives the visitor exactly what they came for and nothing else is needed. ## High bounce rate: not a problem when one page answers the visit High bounce rate looks alarming, but the number only records that a visitor saw one page and left. It never records whether they left satisfied or frustrated, and those two visits look identical in the report. Picture a Laval plumber's contact page. Someone searches for an emergency plumber, lands on the page, reads the number, calls, and closes the tab. Google records a single-page session, a bounce, yet the visit did what the page exists to do. The same holds for a blog post that answers one narrow question in full: the reader gets the answer and has no reason to click anywhere else. In both cases the visit ended because the reader had what they came for. So the number on its own settles nothing. I read it beside time on page, goal completions, and phone call tracking before I decide whether a page needs work, because any one of those can turn a worrying figure into ordinary, healthy behaviour. ## Bounce rate in Universal Analytics: a session with a single page hit A [bounce](/en/glossary/#taux-de-rebond) in Universal Analytics is a session where Google records a single page hit and no other interaction hit. The visitor lands, nothing else fires, and the session closes on that one hit. That definition explains why a high figure carries less weight than it looks: the session simply contained one tracked interaction and nothing more. If your setup is not recording scroll depth, outbound clicks, or video plays as events, plenty of engaged visits still register as bounces, because Google never received a second hit to prove the person stayed. The same gap explains a detail worth understanding: average time on page cannot be measured for a bounced visit. Universal Analytics works out time on page by comparing the timestamp of one hit with the timestamp of the next one. A bounce only ever produces a single hit, so there is no second timestamp to subtract, and the session is counted as zero seconds no matter how long the person actually read. A page full of people who read carefully for two minutes and then leave can still report a high bounce rate and almost no time on page. Before I draw any conclusion from a client's bounce rate, I check how their events are set up. The data only reports what it was configured to capture. ## Page types where a high bounce rate is normal Some pages exist to hand over one piece of information and send the visitor offline, so a high bounce rate on them usually means the page succeeded. A menu page, an hours page, a directions page, a contact page with a phone number: the visitor reads what they came for and then acts away from the screen. A Montréal restaurant's menu-and-hours page and a Laval clinic's directions page both do their job the moment the visitor has what they need, and that moment happens on the first and only page they see. On a one-page contractor site the whole visit is often reading the phone number and dialling it. One more case matters on a bilingual site. Someone who lands on the English page and switches to the French version has created a second pageview, so that visit is not a bounce at all. Language switching lowers the bounce rate on bilingual pages, which is worth remembering before you compare one language against the other. ### Menu, hours and phone-number pages a customer reads and then calls Menu, hours, and phone-number pages are built to be read once and then left, so their bounce rate says almost nothing about quality. A restaurant, a salon, or any local shop puts these details up so a customer can pick up the phone, and once they have the number they go. Analytics cannot see the call, so the visit looks like a plain exit. I tell business owners across Greater Montréal to watch call volume on these pages instead of bounce rate, because the call is the result the page was built to produce, and it is the only number that tells you the page is working. ## Page types where a high bounce rate signals a problem On pages built to move a visitor toward a next step, a high bounce rate paired with a low time on page is a real warning that people are not finding what they expected. A landing page whose headline does not match its offer, a product page missing images or pricing, a service page that never earns trust or shows a clear contact path, a pricing page with no obvious action: these are the pages where a quick exit points to a problem in the page itself, before you question the traffic. A visitor who arrives ready to buy or book and leaves in a few seconds is telling you the page did not carry them forward. On pages like these I start with the page itself before I question where the visitors came from. Reviewing the message match, the layout, and the tracking that sits underneath them is the kind of work an [SEO audit](/en/services/seo-audit/) covers. ## Time on page, events and goal completions: what to read alongside bounce rate Time on page, events, and goal completions are the three numbers I read next to bounce rate, because together they show whether a single-page visit still did its job. Say a visitor spends a minute and a half on a contact page and that session fired a phone-number click event. That visit succeeded, and only the event makes it visible in the report. Goal completions confirm whether the visitor did what the page needed before leaving, whether that is a form, a booking, or a tracked call. Events capture the smaller actions along the way, a video play, a scroll, a button press. Time on page, read for the visits that were not bounces, tells you whether people are actually reading or just glancing and going. When those three line up with a high bounce rate, the page is working and the figure is nothing to fear. When they contradict it, when nobody stays and nothing fires, that is the signal to dig into the page. ## Bounce rate checklist before you change a page Run this short check before you touch a page with a high bounce rate, so you fix a real problem instead of rebuilding a page that already works. - Confirm the traffic source, since paid, organic, and direct visitors behave differently on the same page and each one deserves its own read. - Check the time on page and whether any goal fired during those sessions. - Ask whether the page was built to send people somewhere else, like a contact page or a thank-you page, in which case a fast exit is the plan working. - Confirm your events are recording the interactions that matter, so a tap on a phone link or a language switch is not silently counted against the page. If the answers say the page is working as intended, leave it alone and spend the effort where a number and a purpose disagree. Further reading: for a similar project on a small-business site, see [Café Chasca](/en/cafe-chasca/). ## Go further - **Service:** [SEO Audit for Montreal Businesses, Know Exactly What’s Holding You Back](https://socialinfluencebuilder.com/en/services/seo-audit/) - **Case study:** [Café Chasca](https://socialinfluencebuilder.com/en/cafe-chasca/) - **Glossary:** [Digital marketing glossary: Bounce Rate](https://socialinfluencebuilder.com/en/glossary/#taux-de-rebond)