I have always told myself I am a "power user." I use keyboard shortcuts. I know Vim. I have strong opinions about terminal color schemes. So when I caught myself with 47 tabs open at 11 AM on a Tuesday, I did what any rational person would do: I blamed the browser.
"Chrome is the problem," I muttered, closing five tabs I did not recognize. "It lets me open too many."
But then I stopped. If I was so disciplined, why did I have 47 tabs? Where did they come from? And more importantly — how many had I opened that week without even noticing?
I decided to find out. For seven days, I logged every single tab I opened. Every new tab. Every link in a new tab. Every "let me just check this real quick" that became a permanent resident of my tab bar. I used a simple browser extension to auto-log URLs and timestamps, and I kept a notebook for context: what was I doing when I opened it? Did I need it? Did I ever go back?
The results were not flattering. They were horrifying.
The Numbers
Here is what one week of honest tracking revealed:
Let me put that in perspective. I opened a new tab every 6.7 minutes during my waking hours. I spent almost an hour a day just dealing with tabs — closing, organizing, searching for the one I needed, or staring at the bar wondering what half of them were. And nearly 90% of them were digital litter. I opened them, glanced at them, and never returned.
The Five Types of Tab I Opened
Looking at the logs, my 847 tabs fell into five distinct categories. I had never thought about my browsing this way before. But once I saw the patterns, I could not unsee them.
Type 1: The Curiosity Glance (61% of tabs)
These were the "let me just check" tabs. A link in a Hacker News comment. A product mentioned in a Reddit thread. A Wikipedia article linked from another Wikipedia article. A definition I did not know. A tweet someone referenced.
I did not need these tabs. I needed a preview. I needed to see the headline, verify the claim, or read the first paragraph. But my browser does not do previews. It does tabs. So I opened a tab, got my answer in 8 seconds, and left the tab open "just in case." Just in case what? I did not know. But I did it 517 times in one week.
Type 2: The Deferred Decision (18% of tabs)
"I will read this later." The article looked interesting. The video seemed relevant. The documentation page might help with tomorrow's task. I did not have time now, so I opened a tab and told myself I would come back.
I came back to 12 of them. Out of 152. The rest joined the graveyard. By Friday, my tab bar was a museum of my abandoned intentions. Each one was a tiny debt I owed my future self. And my future self was drowning in interest payments.
Type 3: The Context Switch (11% of tabs)
These were work-related. I was writing in Google Docs and needed to check a source. I was coding and needed to look up a function. I was in Slack and someone shared a link. These tabs felt legitimate. They were work. But each one was a full context switch — unload my current mental model, load a new page, find what I need, then try to return.
The problem was not that I needed the information. The problem was that I needed it in a new universe. My doc disappeared. My code editor disappeared. My thread of thought disappeared. And when I came back, I spent 2-3 minutes remembering where I was. Ninety-three times in one week. That is 4.6 hours of just... re-orienting.
Type 4: The Dreaded Duplicate (7% of tabs)
I opened the same page multiple times because I forgot I already had it open. I searched for "python list comprehension" on Monday, Wednesday, and Friday. Each time I opened a new tab instead of finding the old one. I had three tabs of the same Stack Overflow answer. I had four tabs of the same GitHub repo. I had two tabs of the same Google Doc.
My tab bar had become so crowded that finding an existing tab was harder than opening a new one. So I opened new ones. The clutter created more clutter. It was a positive feedback loop of chaos.
Type 5: The Genuine Keep (3% of tabs)
These were the tabs I actually needed open for hours. My email. My calendar. The main document I was writing. The primary codebase I was editing. Twenty-three tabs out of 847. Less than 3%. Everything else was noise.
The Psychology of Why I Could Not Stop
The numbers were embarrassing, but the psychology was worse. I started noticing my own triggers. I opened tabs when I was stuck on a hard sentence. I opened tabs when a notification made me anxious. I opened tabs when I was waiting for a page to load — a new tab as a distraction from waiting for another tab.
Opening a tab had become a nervous tic. It was the digital equivalent of pacing. When I did not know what to do next, I opened a tab. When I was bored, I opened a tab. When I was avoiding a difficult task, I opened a tab. The browser was not a tool anymore. It was a fidget toy.
And the tab bar itself became a source of anxiety. The more tabs I had, the more stressed I felt. But closing them felt like loss. What if I needed that article? What if that reference was important? Each tab was a potential future value, and closing it felt like throwing away a lottery ticket. Never mind that the lottery was rigged and I never won.
The Wednesday Meltdown
Wednesday was my worst day: 34 tabs at peak. I remember the moment. I was writing a blog post (this one, actually — yes, I am meta). I needed to check a statistic. I opened a tab. Then I saw a related article. Then I needed to verify the source of that article. Then I saw a tweet embedded in that source. Then I clicked the tweet. Then I clicked a link in the tweet. Then I forgot what statistic I was looking for.
I stared at my tab bar. It was a strip of favicons I no longer recognized. I had a tab open for a Japanese knife-sharpening tutorial. I do not own Japanese knives. I had a tab open for a 2017 conference talk about Erlang. I do not use Erlang. I had three tabs of the same Wikipedia page about attention residue. I had opened the third one because I could not find the first two.
I closed them all. Every single one. I pressed Ctrl+W until the browser was silent. Then I sat there, looking at my one remaining tab, and realized I had no idea what I was originally writing.
It took me 23 minutes to get back into flow. I timed it.
What I Changed (And What Actually Worked)
After the meltdown, I tried three fixes.
Fix 1: The 10-Tab Rule (Failed)
I told myself I could never have more than 10 tabs. Every new tab required closing an old one. This lasted six hours. The problem was that closing tabs is a decision, and decisions are expensive. I spent more time agonizing over which tab to close than I would have spent just opening a new one. The 10-tab rule created decision fatigue. I abandoned it by dinner.
Fix 2: OneTab Cleanup (Partial)
I installed OneTab and started collapsing sessions at the end of each day. This helped with the graveyard problem. My RAM usage dropped. My browser stopped crashing. But it did not fix the root cause. I was still opening 100+ tabs a day. I was just burying them more efficiently. OneTab was a cleanup crew, not a prevention strategy.
Fix 3: GoPeek (Actually Worked)
I had built GoPeek, but I had never used it as my own primary workflow. I decided to try it properly. For the second week, I kept the tab logger running, but I used GoPeek for every "let me just check" moment. Hover a link. Preview it. Close it. No tab.
The difference was immediate and absurd.
My curiosity-glance tabs dropped from 517 to 41. That is not a typo. I went from 517 "just checking" tabs to 41. The other 476 became previews that I opened, read, and closed in seconds. My peak tab count on Wednesday was 9. Not 34. Nine.
My context-switch tabs dropped too. When I needed to reference a source while writing, I used GoPeek's sidebar mode. The source stayed visible on the right. My document stayed on the left. I did not "switch" contexts. I expanded my context. I could copy a quote and paste it without ever losing my cursor position.
And the duplicate tabs? Gone. When I needed to re-check something, I did not hunt through a crowded tab bar. I just hovered the link again. The preview was instant. There was nothing to lose.
Week 2 vs. Week 1: The Numbers
Five and a half hours. That is not a productivity hack. That is a part-time job I was doing for free, and I just fired myself from it.
What I Actually Learned
The experiment taught me three things I did not expect.
First: I was not a power user. I was a power opener. There is a difference. Real power users do not have 47 tabs. They have 5 tabs and a clear intention for each one. My tab bar was not a dashboard. It was a confession of my own distractibility.
Second: tabs are not bookmarks. I had been treating them like bookmarks I would read later. But bookmarks are deliberate. Tabs are impulsive. A bookmark is a decision to save something. A tab is a decision to avoid deciding. I was using tabs to defer commitment, and the deferred commitments were eating my RAM and my attention.
Third: the browser is not designed for how I actually work. The browser assumes every link is a destination. But most of my links were waypoints. I did not want to move into the Wikipedia article about Byzantine architecture. I wanted to glance at it while reading about the Hagia Sophia. The browser forced me to move. GoPeek let me look.
What I Do Now
I still have tabs. I have 4 to 6 at any given time. My email. My calendar. The main thing I am working on. A reference I need for the next hour. That is it. Everything else is a preview.
When I see a link I want to check, I hold Shift and hover. The preview opens. I read what I need. I close it. If I need it for longer, I drag it to sidebar mode. If I need it later, I bubble-minimize it. But I do not open a tab unless I am committing to that page as a primary workspace.
My browser is quieter now. My tab bar is readable. My RAM stays under 2GB. And when I sit down to write, I write — instead of spending twenty minutes cleaning up the debris of yesterday's curiosity.
I tracked every tab for a week, and what I found was not a browser problem. It was a behavior problem. And the behavior was driven by a tool that demanded commitment for every glance. I fixed the tool. The behavior followed.