On this page
- Start with one question
- Pick the visits that can answer it
- Scan the Activity list first
- Let the quiet stretches go
- Change speed as you go
- Use the keyboard
- Take notes in one line per replay
- Stop after a set number
- When a whole visit is worth it
- A sample 25-minute session
- Frequently asked questions
- Try it on your site
- Sources
One narrow question keeps session recordings from eating hours. Open only the visits that can answer it, pause each one to read its Activity list first, leave idle skipping on and speed past what you already understand. Stop after ten replays or 30 minutes, then make one change.
Session recordings are easy to collect and slow to watch. Open one with no plan and it leads to another, and then the afternoon is gone. A fixed routine keeps each sitting to about 25 minutes.
Key takeaways
- Write one narrow question before you open a replay, and close any visit that never gets near it.
- Leave idle skipping on, and press S to turn it off only when waiting is what you're studying.
- Use 4x or 8x for browsing you already understand, 1x around the moment that matters and 0.5x for fast bursts.
- Learn the shortcuts: Space plays or pauses, J and L jump 10 seconds, the arrow keys jump 5, S toggles idle skipping, F goes full screen and Esc closes.
- Stop after ten replays or 30 minutes, then make one change and come back with the same question.
Start with one question
Before you open a single replay, write down what you want to know. Keep it narrow enough that one visit could answer it.
- "Why do people leave the travel mug page without adding it?"
- "Does anyone find the size guide on the jacket page?"
- "Can phone visitors use the new menu?"
A question tells you which visits to open, which moments matter and when you're done. "What are visitors doing?" has no finish line, so skip it. Write the question at the top of your notes.
Pick the visits that can answer it
The replay list shows each visit's start time and length, and a small dot marks replays you haven't opened yet. Use those, and the first row of each Activity list, to choose before you watch.
- For a landing page question, keep the visits whose first Activity row is a Page view of that page. Short ones are the visitors who gave up early.
- For a path question, like the size guide or the menu, open longer visits. A visit of a few seconds rarely gets that far.
- For a question about one page, first find where visitors leave in your reports, as seeing what customers do on Shopify or why visitors leave a Wix site shows, then open visits from that period and check whether they reached the page.
- For replays you saved earlier, open the Starred tab.
If you have fewer visits than you expected, see why some visits aren't recorded.
Start from the heatmap
When the question is about one page, let the map pick the spot first. Open Heatmaps in Session Recordings, pick the page and the device, and read the Rage clicks and Did nothing views for the last 7 days. Then open visits from those days to see what visitors were trying to do there. More on how the heatmaps work.
Scan the Activity list first
A replay starts playing as soon as you open it. Press Space to pause, and read the list beside it before you watch anything. The Activity list shows the visit in order: a Page view row for the page the visitor landed on, then each Click and Typing (masked) where someone typed. Click any row to jump straight to it.
Treat the list like a table of contents. Clusters of Click and Typing rows mark where the visitor was busy. Jump to the first cluster, and if the page on screen has nothing to do with your question, close the visit and open the next one. That check takes seconds. If several visits in a row never get to what your question is about, that's a finding too: write it down.
When a visit does reach it, start a step early. Click the row just before it and play forward. The lead-up is usually where the cause is.
Let the quiet stretches go
Visitors leave tabs open. They read, answer messages and wander off. In Session Recordings, any stretch of more than 10 seconds with no mouse movement, clicks, taps, scrolling or typing is skipped, and skipping is on by default. A visitor who left your page open for ten minutes doesn't cost you ten minutes.

Leave skipping on as a rule. Turn it off when your question is about waiting. If you suspect a page is slow, the long pause is the finding, and you want to see it at its real length.
Change speed as you go
The player runs at 0.5x, 1x, 2x, 4x and 8x. Give each speed a job.
- 8x for long stretches of browsing you already understand, like a visitor paging through a collection
- 4x for browsing that has nothing to do with your question
- 2x for following a visitor from page to page
- 1x around the moment that matters, so you catch each click and scroll
- 0.5x for fast bursts, like a flurry of taps on a phone or a menu that opens and closes
Slow down the moment something surprises you. Speed is for the parts you already understand.
Find the moments worth watching
Jump to any moment from the Activity list, skip the quiet parts, watch at up to 8x and star the replays worth keeping.

Use the keyboard
Six shortcuts save most of the clicking. Press ? while a replay is open, or click the keyboard icon in the player's controls, to see the list.
| Key | What it does |
|---|---|
| Space | Play or pause |
| J / L | Back or forward 10 seconds |
| ← / → | Back or forward 5 seconds |
| S | Turn idle skipping on or off |
| F | Full screen |
| Esc | Close the replay |
In practice: click the Activity row just before the moment you care about, press Space to play, and when something happens too fast, press ← to go back 5 seconds and watch again at 1x. Press L to jump 10 seconds past a part you've seen, and Esc to close the replay and open the next one.
Take notes in one line per replay
Keep a document or spreadsheet open while you watch, and write one line per replay in the same shape every time.
Oct 3, 2:14 PM · 1:15 · Wanted a gift under $30. Tried the menu, then search. Stopped on an empty results page.
Wanted, tried, stopped. It makes you describe what the visitor was trying to do, which is easy to lose once you start following clicks. The date, start time and moment at the front tell you, or a teammate with access to your dashboard, where to find the visit again.
When a replay shows the problem clearly, star it. Starred replays are kept past the usual 30 days, and the Starred tab brings them back.
Stop after a set number
Decide when you'll stop before you start. Ten replays or 30 minutes, whichever comes first, is a sensible place to begin.
Stop early if any of these happen.
- You've seen the same problem several times. You have your answer.
- The visits aren't answering the question. Rewrite it and start again.
- You're tired. Tired eyes make everything look like a problem.
Then act. Make one change, and come back later with the same question.
When a whole visit is worth it
Two situations call for watching a visit from start to finish at 1x.
- When you're new to replays. Watch two or three ordinary visits in full. You'll learn what a normal visit to your site looks like, and that makes odd moments jump out later, even at 4x.
- When one visit is all you have. If a customer reports a problem and you find their visit, watch all of it. The cause can sit minutes before the moment they noticed it. Then write it up as a clear bug report.
No visits of your own yet? The empty Replays page in Session Recordings has a Watch a sample replay button, a made-up visit to a demo shop, which is enough to try the keys above.
A sample 25-minute session
- Write the question. (1 minute)
- Choose up to ten visits from the list and scan their Activity lists. (4 minutes)
- Watch each one, jumping to the key moment and changing speed as you go. (16 minutes)
- Read your notes and write one sentence that answers the question. (3 minutes)
- Star the clearest replay and write down one change to make. (1 minute)
Put it on your calendar once a week and keep a running list of open questions. Take the top one into each session, and when it's answered, move it to a done list along with the change you made. After a few months, that list is a plain record of what you learned about your visitors.
Once you're ready to watch with a list of things to check, see what to look for in your first 20 replays.
Frequently asked questions
Do you need to watch every session recording?
No. Watching everything is slow, and many visits have nothing to do with your question. Pick one question, choose the visits that can answer it, and stop once the same problem shows up several times. Star the clearest examples so they're kept, and let the rest go when your retention period ends.
What does idle time mean in a session replay?
Idle time is a stretch when the visitor did nothing on the page: no mouse movement, clicks, taps, scrolling or typing. It can mean careful reading, a switch to another tab, a slow page or a break away from the screen. A single pause rarely tells you which. Look at what happens right before and after it, and compare with other visits to the same page.
Can a tool pick the important replays for me?
Some can. Microsoft Clarity, for example, flags rage clicks, dead clicks, excessive scrolling and quick backs, so you can filter to sessions that show them. Session Recordings marks rage clicks and clicks that did nothing on its heatmaps, so you can see which page and element to look into; inside a visit, fast repeated clicks show as one row with a ×N count in the Activity list. To weigh that against other tools, see free session recording apps for Shopify or session recording tools for Wix compared.
How do you avoid reading too much into one replay?
Treat each replay as one story, not a trend. Write down what you saw, then look for the same behavior in other visits before you change anything. Keep a count next to each finding, and check your analytics to see how often it happens across all visits. Watching with one question in mind also keeps memorable but unrelated visits from steering you.
Try it on your site
Session Recordings has the player described here free: idle skipping, speeds up to 8x and the keyboard shortcuts. See everything that's free.



