Free Bounce Rate and Engagement Rate Calculator
Enter sessions and engaged sessions from a Google Analytics 4 report to see the engagement rate and the bounce rate. The two figures are opposites, and they always add up to 100 percent of the sessions you enter.
This is a calculator, not a Google ranking score. There is no universal good bounce rate, and bounce rate is not a Search ranking factor. A clearly labelled legacy mode is available if you still have a Universal Analytics style count of single-page sessions.
Calculation mode
Totals from your report
Optional page comparison
Add rows if you want to compare similar pages over the same date range. Leave this empty if you only have totals.
Page comparison
Improvement checklist
These reminders can help you review a page. They are not a Google score, and they do not change the percentages above.
Report
Copy this if you want a text record of the inputs and the rates. This page does not change your Analytics property or your site.
Checks
No items in this filter.
What the tool calculates
This page is a calculator for figures you already have in a report. In Google Analytics 4, engagement rate is the share of sessions that were engaged. Bounce rate is the share of sessions that were not engaged. The two rates are opposites. If you enter 10,000 sessions and 6,200 engaged sessions, the engagement rate is 62 percent and the bounce rate is 38 percent.
Google’s help article on engagement rate and bounce rate defines an engaged session as a session that lasts longer than 10 seconds, or has a key event, or has 2 or more page or screen views. This tool does not connect to your Analytics account, so it cannot test those conditions for you. It only applies the formulas to the numbers you type.
A clearly labelled legacy mode is available for older Universal Analytics style counts. In that older product, bounce rate was single-page sessions divided by sessions. That is not the same as the GA4 inverse of engagement rate. If you still have a legacy export, you can calculate the older percentage here, but you should not mix it with a GA4 figure and treat the difference as a writing trend.
The input checklist score is not a grade of your bounce rate, and it is not a Google score. It only summarizes whether the totals can be used and whether any cautions apply, such as a small sample or the use of legacy mode. There is no universal good bounce rate. A short definition page and a long tutorial should not share one target.
Bounce rate is also not a Search ranking factor. Google has said it does not use Analytics data as a ranking signal. Use the percentages to understand your own traffic, not to chase a ranking formula.
How to use it
Open a GA4 detail report that includes sessions and engaged sessions. An Editor or Administrator can add those metrics if they are not already visible. Copy the totals for the date range you care about, then paste them into the two fields on this page.
Leave the mode on GA4 unless you are deliberately working with an older Universal Analytics export. If you switch to legacy mode, the second field becomes single-page sessions, and a banner reminds you that the complement of that bounce rate is not a GA4 engagement rate.
If you want to compare a few pages, add a row for each one. Use similar pages over the same date range. A how-to guide and a short definition can both be useful and still show different rates. The table will list each valid row, and a warning will appear if a row cannot be calculated, for example when engaged sessions are larger than sessions.
You can load a sample if you only want to see how the results are laid out. The sample is a demonstration, not a live report and not a target. When you are done, use Reset to clear the form. Copy report and Download report give you a text record of the inputs and the rates. Nothing is uploaded, stored, or sent over the network, and the page does not use cookies or local storage.
If a result looks impossible, check the source report before you rewrite a post. A missing tag, a broken event, or a consent banner that never loads Analytics will distort every percentage this calculator can produce.
How to read the rates and the checks
Start with the two large percentages. In GA4 mode they will always add up to 100 percent of the sessions you entered. The explanation under the cards restates the official definition, including the “longer than 10 seconds” test, so you can keep the wording next to the numbers.
Then read the checks. A pass means the totals can be calculated. A warning might mean you are in legacy mode, the sample is very small, or a page row is invalid. Info items remind you that there is no official good rate, that bounce rate is not a ranking factor, and that first_visit, first_open, and session_start are excluded from the key-event test even if they are marked as key events.
The improvement checklist is a review list, not a scoring system. It covers search intent, a readable first screen, speed and mobile layout, useful internal links, ad placement that does not hide the article, fair comparisons, and a measurement check. Those are the same practical steps described in the related blog post on this site.
Give a date range enough sessions to be useful. Fewer than 100 sessions can swing after a few visits, and even a few hundred sessions should be read as a pattern, not a verdict. Compare a page with similar pages, and compare a page with itself after a change, rather than against a chart of “average bounce rates” that has no official source.
If you recently changed a title, the first paragraph, the template, or your ads, wait until the new period has a fair sample before you decide the change worked. This calculator will not tell you that a rewrite succeeded. It will only help you do the arithmetic consistently.
One more caution about the two modes. Session timeout is not the same as the 10-second engagement test. By default, a GA4 session times out after 30 minutes of inactivity. That setting decides when one session ends and another can begin. It does not decide whether a session was engaged. This calculator does not apply a timeout rule. It only divides the numbers you enter.
If you publish both a website and an app, remember that the official wording is “page or screen views.” A second screen view can engage a session the same way a second pageview can. When you compare rows, keep website pages with website pages unless you have a clear reason to mix them.
What this tool cannot do
It cannot log into Analytics, read your property, or confirm that a session lasted longer than 10 seconds. It cannot see key events, pageviews, or screen views. It cannot judge whether a title matches a query, and it cannot measure page speed. Those checks still need the report and the published page.
It does not set a target bounce rate, and it does not predict rankings, snippets, or clicks. It does not change your site or your Analytics configuration. If you want a lower bounce rate because people cannot start the article, fix the first screen, the speed, the links, or the ads. If people arrived, got a short answer, and left, the rate may be telling you something ordinary, not something broken.
Use the calculator as a pocket tool for the arithmetic, then go back to the page a visitor actually sees. Read the title, the first screen, and the next internal link the way a new visitor would. That is the work this tool is trying to support, and it is also why a percentage alone is never the full story.