Why is my bounce rate so high: check the count

A bounce is not a visitor who hated the page. In Google Analytics 4, a session counts as engaged when it has a second page view, triggers a key event such as a sign-up, or lasts long enough to register engaged time. Every other session is a bounce. So someone who reads your only page for a minute and closes the tab counts as a bounce. So does a visit that ends on a payment or booking page on another domain, because the visit on your site ended there and a new session started on theirs.

• Your bounce definition: does a long read with no click count as engaged in your tool?
• Links to other domains: payment, booking or help pages that end the visit on your site.
• Tags that wait for a cookie banner, so a fast visit ends before its page view is recorded.
• The first screen: is there one clear next step, or only a header menu and a footer?
• Phones: a banner, pop-up or slow hero image covering the first screen before anyone reads it.

Open the report that shows bounce rate for your landing page, and read it next to the engagement rate for the same page. A high bounce rate with short visits points at the first screen or a page that loaded slowly. A high bounce rate where a few visits run long usually means some visitors read while most left at once, so compare the traffic sources, not the average. Next, confirm the tag fires on a real visit. Load your page in a private window with the real-time view open and watch for your own visit. If it never appears, the number is wrong before the page is.

Payment pages, booking widgets and help desks often sit on their own domain. A visitor who follows a link there leaves your site, and the analytics tool starts a new session on the other domain unless cross-domain tracking is set up. The visit on your side then shows one page and no event, which counts as a bounce. The purchase may happen later on the other domain, but the first visit still shows as a bounce. Look at the bounce rate on the pages that send people out. A page with a high bounce rate and a link to another domain usually points at the handoff, not at the content.

Some visitors read the first screen and still leave. The screen has a headline, a paragraph and a header menu, but no button that starts the thing they searched for, so nothing gets clicked. List everything a stranger could click on that screen. If the only action is a header link that says About, the visitor has nowhere to go. A simulated visitor with the same search in mind reads the same screen and reports whether it found a next step, and which one. The fix is a single action above the first scroll, labeled with what happens after the click.

Landing page testing

On a phone, the first screen is most of the page the visitor sees. A cookie banner, a newsletter pop-up or an autoplaying video can cover the headline and the main button before anyone reads a word. A large hero image on a slow mobile connection leaves a blank area first, and some visitors leave in that gap. Test the page on your own phone over mobile data, not on office Wi-Fi. Mimiq's browser records relevant JavaScript errors and failed or slow app requests on the step where they happen, so a visitor who gave up on a blank hero shows up next to the request that stalled.

Each new tool that sends people to another domain can change the count without the page changing, so check the bounce rate again after every one. Rerun the same simulated visitors after each fix to the first screen, to see whether the next step is clearer. Run the handoff through to the payment step too, since a link that breaks there never shows up in the landing page numbers.