Somewhere in a small town in the Netherlands, a bakery owner named Ilse runs a site that loads in about four seconds on a good day and nearly nine on mobile over 4G. People find her through search, land on a page, look around, and leave in seconds. She tells me she has "good content." She probably does. But the page loads slowly, the opening paragraph is a wall of text with no clear answer, and the navigation offers them nowhere to go next. So they go back.
The search result they came from gains a click. Her page gains a bounce. And dwell time—the one metric that actually captures whether a page did its job—tanks.
I have spent enough time staring at analytics dashboards to know that the single biggest lever for improving dwell time is not a technical trick. It is the content itself. But it is the content combined with speed, structure, and a reason to keep scrolling. Here is how I approach it, and what I got wrong along the way.
Key Takeaways
- Dwell time is not the same as time on page. It is the time between clicking your result and coming back to search—so it lives in the SERP, not in Google Analytics.
- A "good" dwell time depends on intent. For a quick factual query, five seconds can be fine. For a comparison or a tutorial, a minute or more is the real target.
- Most dwell time problems are content problems: wrong intent match, bloated opening paragraphs, no visual anchors, no forward path.
- Speed still matters. A page that takes four seconds to render has already spent most of a reader's patience before a single sentence is read.
- Small structural changes—a summary line, a table of contents, one relevant video—often move the needle more than rewriting every word.
What dwell time actually measures (and what it doesn't)
There is a lot of confusion floating around, so let's clear it up. Dwell time is the gap between a user clicking your search result and hitting the back button to return to the results page. That is it. It measures whether the reader found what they needed, or whether they gave up and went looking elsewhere.
It is not a confirmed ranking factor. Google has never said publicly that it uses dwell time directly. But it is a strong proxy for satisfaction, and satisfaction feeds into how your pages perform over time. When users return to search quickly after visiting your page, the signal is clear: your page did not deliver.
Now the comparison that matters:
| Metric | What it measures | Where to find it | What a "bad" value looks like |
|---|---|---|---|
| Dwell time | Time between click and return to SERP | Not directly in GA4—must be inferred | Under a few seconds for most intents |
| Time on page | Time between two pageviews in the same session | GA4 engagement metrics | Under 30 seconds on a long-form page |
| Bounce rate | Sessions with no interaction | GA4 | Over 80% on a page designed to inform |
Here is the honest problem: dwell time is not directly measurable in Google Analytics. It happens outside your site, in the search interface. You infer it by looking at return-to-SERP behaviour, or you approximate it through engagement time and scroll depth. Anyone claiming to show you a clean dwell time report is either using a third-party tool or guessing.
What is considered a good dwell time?
There is no universal number, and anyone who gives you one is oversimplifying. What counts as "good" depends on the search intent behind the query. For a navigational search—someone looking for a specific brand or login page—a few seconds is normal and healthy. The user found the link, clicked, got what they needed.
For informational queries, the bar is higher. A reader landing on a comparison article or a how-to guide should be staying at least 30 to 60 seconds if the content is doing its job. For a detailed tutorial, several minutes is not unusual. The rule I use: if a page exists to answer a question, and the average reader leaves in under ten seconds, the page is failing.
Rather than chasing a benchmark, compare your pages against each other. A page with a 20-second average on a topic that clearly requires two minutes of reading is your problem page. That is a more useful signal than any external average.
The 80/20 of dwell time: where your effort actually pays off
The 80/20 rule in SEO, in this context, means that a small number of changes tend to produce most of the improvement. You do not need to rewrite your entire site. You need to fix the handful of things that reliably kill a reader's attention.
From my own testing, the biggest offenders are almost always in the first few seconds of the visit:
- A slow first paint. If the page takes more than three seconds to show readable content, you have already lost a large share of mobile visitors.
- A vague opening. The first paragraph is the highest-value real estate on the page, and most sites waste it on throat-clearing.
- No visual break in the first screen. If the reader sees only a dense block of text, they leave.
- Nothing to click next. No internal links, no related articles, no table of contents—just a dead end.
Fixing those four things is boring work. It is also where the compounding returns are. A single well-placed summary box at the top of a long article has, in one of my projects, raised engagement time on that page by roughly a third. That is not magic. It is just giving the reader a reason to stay past the first glance.
How to improve page load time?
Speed and dwell time are directly linked, because a slow page burns a reader's patience before they have read a word. The most reliable fixes are structural rather than clever:
- Compress and convert images. Serve modern formats like WebP and size them correctly for the viewport. Oversized hero images are one of the most common culprits.
- Defer non-critical JavaScript. Scripts that run on page load and block rendering are what make a page feel sluggish even when the network is fast.
- Cut the CSS and font weight. Loading three font families and a bloated stylesheet is unnecessary for most sites.
- Cache aggressively and use a CDN. For a global audience, this alone can cut load times dramatically.
If you are not sure where the problem is, run a lab test and look at the LCP figure—the time it takes for the largest visible element to render. It is the metric that most closely tracks what a reader actually perceives as "loaded."
Rewriting the opening: the highest-leverage content change
The first paragraph is where dwell time is won or lost. Most pages fail here not because the writing is bad but because it is wrong for the moment.
A reader arriving from search has a question. They want the answer to appear, or at least to be visible as reachable, within the first few lines. If your opening paragraph explains the history of the topic, defines things the reader already knows, or tells them what they are about to learn, you have wasted their patience. So they leave.
The fix I apply, over and over: state the answer, or clearly signal where it comes, in the first two sentences. Then build the rest of the section around the why. Not the other way around.
I once spent two weeks rewording every paragraph of a long guide, polishing the language, and saw almost no change. Then I rewrote just the opening paragraph—three sentences, plain answer first—and time on page moved noticeably within a week. The lesson stung: the words were fine, the order was wrong.
Structural changes that quietly add seconds
Beyond the opening, a few small additions consistently buy you more time with the reader:
- A short table of contents near the top, so the reader can see the page is substantial and jump to what matters to them.
- Scannable subheadings that answer specific sub-questions, so a reader skimming finds a reason to stop and read.
- One relevant visual—a screenshot, a diagram, a short video—placed where the text otherwise becomes dense.
- Contextual internal links that invite the next click, keeping the reader on your site instead of sending them back to search.
Note that these are not tricks. They are the same things you would want as a reader. That is the test I use: if I landed on this page cold, would I stay? Be honest. Often the answer is no, and that honesty is the start of the fix.
Does more traffic change any of this?
A question that comes up whenever dwell time is discussed: is it worth chasing raw traffic, or does quality of visitor matter more? Both matter, but not in the way people assume.
How to get 1000 website visitors per day?
There is no shortcut that reliably produces a thousand daily visitors, and any source promising one is selling something. What actually works is a combination: a cluster of pages that each target a distinct search intent, strong internal linking so readers move between them, and enough time for those pages to accumulate authority. Realistically, reaching that volume takes months of consistent publishing and refinement, not a single tactic.
And here is the important part—more traffic does not improve dwell time. It can make it worse. If you flood a page with visitors whose intent does not match the content, your average dwell time drops and the pages look less useful. Getting a thousand visitors per day to the wrong page is worse than getting two hundred to the right one.
So when I hear people ask how to scale traffic, my honest answer is: fix the pages you already have first. Improve dwell time on your existing top pages before you chase volume. The readers who are already arriving are telling you, through their behaviour, exactly what is wrong. You just have to look.
A short list you can act on this week
Dwell time is not something you optimise once and forget. It is the cumulative result of many small decisions—how fast the page loads, whether the opening respects the reader's time, whether the structure gives them a reason to stay, and whether the content actually answers the question they came with.
If you do nothing else, do this: open your three most-visited pages, read each one as if you had arrived from a search result, and ask whether the answer is visible in the first screen. Then check the load time on a mobile connection. In most cases, those two checks alone will reveal where the problem is.
Ilse, the baker, eventually fixed her page. Faster images, a clearer opening, and a small table of contents. Her average engagement time on that page more than doubled. Not because she wrote better prose—because she gave people a reason to stay past the first five seconds. That is really all dwell time asks of you.
