Average Session Duration

Metricuno
May 17, 2026
4 min read
Quick answer

Average session duration measures mean time spent per visit — a directional engagement signal that's far more useful segmented than as a single store-wide number.

Definition
Engagement metric

Average Session Duration

The mean time visitors spend on your site per session, calculated as total session time divided by total sessions.

Average session duration is the arithmetic mean of how long each session lasts on your store, typically reported in minutes and seconds. GA4 derives it from the time between the first and last event in a session, so sessions with only one event register as zero — which drags the average down on bounce-heavy traffic.

It's a directional engagement metric, not a target to optimise toward. A rising average can mean visitors are exploring more products, or that they're stuck trying to find something. Read it alongside conversion rate, pages per session, and scroll depth before drawing conclusions.

Also known as
Avg. session duration
Mean time on site

The metric sits inside the broader family of ecommerce metrics as an engagement-side signal, paired with conversion-side numbers like add-to-cart rate and checkout completion. On its own it tells you very little about revenue — but compared across segments, it surfaces friction faster than most session recordings will.

The most common misuse is treating a higher number as automatically better. On a product detail page, three minutes is a strong signal. On a checkout step, three minutes means someone is hunting for a discount code or fighting a payment error. Context decides whether the same number is good or bad.

Formula

Average Session Duration = Total Session Duration / Total Sessions

Variables

Total Session Duration

Total session duration

Sum of every session's length in seconds, measured from the first to the last event in each session.

Total Sessions

Total sessions

Count of all sessions in the reporting window, including single-event sessions that contribute zero duration.

Worked example

An apparel store on Shopify pulls 30 days of GA4 data: 120,000 sessions and 360,000 minutes of cumulative session time.

Total session duration: 360,000 minutes (21,600,000 seconds)

Total sessions: 120,000

3 minutes per session (180 seconds)

Three minutes is mid-range for apparel. The team's next step isn't to celebrate or panic — it's to break the number down by landing page and device to see where the average is being pulled up or down.

Benchmarks vary widely by vertical, traffic source, and device. Paid social traffic on mobile typically clocks 60-90 seconds, while organic visitors landing on a buying-guide post can sit above five minutes. The numbers below are realistic ballparks to sense-check your own segments against — not targets.

Benchmark

Typical average session duration by vertical and traffic source (Shopify-style stores, mobile + desktop blended)

VerticalPaid socialPaid searchOrganic searchEmail / SMS
Apparel & accessories1:102:003:202:45
Beauty & skincare1:252:153:453:00
Home & furniture1:402:504:303:30
Consumer electronics1:302:404:003:15
Food & beverage0:551:302:302:10

If your number sits well below these ranges on a high-intent channel like email, the likely culprit is a landing experience that doesn't match the message — a promo email pointing at a cluttered category page, for example. If it sits well above on checkout pages, you have a friction problem worth investigating with session replay.

Frequently asked

Frequently asked questions

No. Long sessions on product or content pages usually indicate interest, but long sessions on checkout or cart pages almost always indicate confusion or technical friction. Always interpret the metric in the context of the page type and step in the funnel.

GA4 measures duration from the first to the last event, including the final event's engagement time. Universal Analytics used the gap between the first and last hit, which excluded the time spent on the exit page. The methodologies differ enough that you shouldn't compare year-on-year across the two tools.

Engagement time only counts seconds when the tab is in focus, so it filters out background tabs and idle time. Average session duration includes the full window between first and last event. Engagement time is the more honest attention signal; session duration is closer to a total-exposure number.

There's no universal target. Apparel stores often land between 1:30 and 3:30 blended across channels, while higher-consideration verticals like furniture or electronics frequently exceed four minutes on organic. The useful benchmark is your own segment-level history, not a global number.

Single-event sessions — a visitor lands, doesn't trigger another event, and leaves — record as zero duration in GA4 because there's no second timestamp to measure against. These bounces drag down the store-wide average, which is why segmenting by engaged sessions usually gives a more useful picture.

Not directly. Google has stated repeatedly that GA4 metrics aren't ranking signals. However, the underlying behaviour the metric reflects — content that holds attention — correlates with rankings because it correlates with content quality and search intent match.

Start with three cuts: traffic source, device, and landing page type. That combination usually surfaces 80% of the diagnostic value — for example, a mobile paid-social cohort with a 30-second average pointing at a slow-loading PDP. Store-wide averages bury these patterns.

In Universal Analytics, yes — idle tabs could keep a session technically alive. GA4 mitigates this by tying duration to events and engagement time, so a tab left open in the background no longer balloons the number the way it used to.

Weakly and non-linearly. Sessions that convert are usually longer than sessions that don't, but pushing the average up doesn't push conversion rate up. Treat duration as a leading diagnostic — useful for spotting friction or interest — and conversion rate as the outcome metric.

Only at the segment level. A store-wide alert is too noisy because traffic-mix shifts move the average without anything actually changing on-site. A useful alert is something like 'organic search session duration on the homepage drops more than 20% week-over-week' — that's specific enough to act on.

Get an AI expert review of your site

Paste your URL — Metricuno's AI runs the same heuristic checks a senior CRO consultant would, scoring your page and prioritising the fixes that'll move conversion fastest.