I Tracked My Browser Activity for 30 Days, Here’s What I Learned

For 30 days, I used Focus Companion to pay closer attention to how I actually work in my browser.

I wasn't trying to eliminate every distraction or achieve a perfect productivity score. I wanted to understand something much simpler: when am I actually focused, and what tends to happen when that focus starts to disappear?

After looking at my browsing patterns and paying more attention to what I was doing while working, a few habits became much easier to see.

I noticed that my focus follows fairly recognizable periods throughout the day. I realized that tabs don't need to contain distracting websites to distract me. I discovered that background music, which might help some people focus, does the opposite for me.

And one of the most interesting patterns came from something that has become a major part of how I work: AI.

When I asked AI to handle a longer task, the waiting time often became an invitation to check my phone, open social media, or start something completely unrelated.

But the biggest lesson from these 30 days wasn't that I needed to stop switching tabs.

It was that I needed to understand why I was switching in the first place.

My focus follows a surprisingly consistent daily pattern

One of the clearest things I noticed was how much my ability to focus changes throughout the day.

For me, 10:00 to 12:00 is usually a very strong period of focus. I can often work during those hours with little or no distraction, and sometimes that focused period continues until around 13:00.

After that, things start to change.

Around 14:00 to 15:00, I find it much harder to maintain the same level of concentration. Even when I deliberately try to focus, I'm much more likely to check my phone, open social media, or switch to something unrelated.

Interestingly, that doesn't mean the rest of my day is unproductive.

I often become productive again between approximately 16:00 and 18:00. I can also start working again around 19:00 without much difficulty.

And then there's the evening.

My strongest focus often appears around 21:00 to 22:30.

Before tracking my browsing and paying attention to these patterns, it was easy to think about productivity at the level of an entire day:

> Today was productive.

or:

> I couldn't focus today.

My experience was much more nuanced.

I could have an extremely focused morning, a distraction-heavy period in the afternoon, and then another excellent period of concentration later that evening.

That changed how I think about my own productivity.

Instead of expecting the same level of focus throughout the entire day, I can recognize the periods when focused work seems to come more naturally to me.

These are my patterns, of course. Someone else's most focused hours might be completely different.

The useful part is discovering your own.

Too many open tabs make me switch more

Another thing I noticed was that a tab doesn't need to contain social media, entertainment, or another obvious distraction to pull my attention away.

Sometimes work-related tabs distract me too.

I might be working on one task while keeping documentation for another task open, an article I'll need later, another project, a tool I'm going to use eventually, and several other tabs that are all technically related to work.

None of them are "bad" tabs.

The problem is that they're not relevant to what I'm doing right now.

When those tabs remain visible, I've noticed that I'm much more likely to move between them.

That was important because it changed the way I thought about switching tabs while working.

The problem wasn't simply:

Focus website → distracting website → focus website.

Sometimes it looked more like:

Current task → another work tab → another idea → another task → back to the original task.

I was still "working," but I wasn't necessarily staying with the same problem.

What helped me: keeping only the tabs I need now

The solution that has worked best for me is surprisingly simple:

I keep open only the minimum number of tabs required for my current workload.

And I've become stricter about what "required" means.

A tab I might need later isn't required now.

Documentation for something I'm planning to work on afterward isn't required now.

An interesting article I want to read isn't required now.

If I'll need something later, I can save it for later.

This makes my browser quieter and reduces the number of possible directions my attention can take.

I'm not trying to achieve some perfect one-tab setup. If my current task genuinely requires several tabs, I'll use several tabs.

The distinction is whether those tabs belong to the current context.

Difficult tasks make me want to switch tabs

Not all of my tab switching was caused by what was already open.

Sometimes it started with the work itself.

I noticed that when a task became difficult and required more thinking, I became much more likely to look for another tab.

Maybe I reached a technical problem I couldn't immediately solve.

Maybe I needed to stop and think carefully about what to do next.

At those moments, switching to something else could feel like a small bit of relief.

This was an important observation because it showed me that closing distracting websites wouldn't necessarily solve everything.

The important moment often happened before I opened the new tab.

So I started trying something very simple.

Before opening another tab, I stop for a moment and ask myself:

> Do I need to open this tab right now?

If I need documentation for the problem I'm solving, then yes.

If I need to search for information directly related to my current task, yes.

But if I don't actually need it now, I try not to open it.

That small pause has been surprisingly useful.

It doesn't prevent me from getting distracted, and I certainly don't remember to do it every time.

What it does is create a moment between wanting to switch and actually switching.

And sometimes that's enough for me to realize that I don't really need to leave the task.

AI became an unexpected source of distraction

One of the most interesting things I noticed during these 30 days was how AI affected my browsing behavior.

I use AI frequently while working, particularly for technical tasks.

AI can make parts of my work considerably faster, but I noticed a strange pattern whenever I gave it something that took a while to process.

I would send the prompt.

The AI would start working.

And suddenly I had a small period where I was waiting.

That was often enough.

I'd check my phone.

Or open social media.

Or switch to another browser tab.

Sometimes there wasn't even a particular reason to check anything. The AI was taking some time, and I automatically looked for something else to do.

The irony is that a tool helping me complete work faster could also create opportunities for me to become distracted.

Starting another task while AI works wasn't the answer

One obvious response is to use that waiting time "productively."

AI is working on Task A, so why not start Task B?

I found that this wasn't necessarily helpful for me.

Now I'm thinking about a completely different problem.

When the AI finishes, I need to leave what I just started, return to the original task, remember its context, evaluate the AI's response, and potentially switch back again afterward.

Instead of filling AI waiting time with unrelated work, I found something that works better for me:

I stay inside the same problem.

If I've asked AI to help with a technical question, there are usually plenty of things I can think about while it works.

I can try to understand the problem more deeply.

I can consider whether there might be a better solution than the one I asked the AI to implement.

I can think about edge cases.

I can question my assumptions.

I can decide how I'm going to verify the answer when it arrives.

And one thing I've found particularly useful is criticizing my own prompt.

Did I explain the problem properly?

Did I provide enough context?

Am I asking AI to implement an approach without first questioning whether it's the right approach?

Is there a simpler solution?

What could the AI misunderstand?

What should I verify before accepting its answer?

I'm still doing something while the AI works, but I'm not opening an entirely new thread of work.

I'm staying within the same context.

When the response arrives, the problem is still fresh in my mind and I'm already thinking critically about the answer I'm about to receive.

For me, that's been much more useful than trying to squeeze an unrelated task into every moment of waiting.

It's also changed how I think about multitasking with AI. Being able to do two things at once doesn't necessarily mean I benefit from doing two unrelated things at once.

Background music is 100% a distraction for me

Another very personal discovery was music.

Some people seem to work extremely well with background music.

I'm not one of them.

When I listen to music while doing focused work, I tend to feel foggier. It becomes harder for me to maintain the same clarity I have when I'm working without it.

But there was another problem I hadn't really considered:

music gave me another reason to switch tabs.

A song would come on that I didn't want to hear.

I'd switch back to change it.

Maybe I'd look for another song.

Maybe I'd change the playlist.

Then I'd return to work.

It was another small interruption that didn't seem important by itself but repeatedly pulled me away from what I was doing.

So for me, the best solution is usually simple:

I work without background music when I need to concentrate.

That doesn't mean everyone should stop listening to music.

If you focus well with music, a different approach might work perfectly well for you. One thing I'd suggest experimenting with is choosing a playlist you already like, starting it, and then leaving it in the background rather than repeatedly returning to manage what's playing.

The lesson I took from this wasn't:

"Music is bad for productivity."

It was:

"Music is distracting for me."

That distinction matters.

Not every tab switch is a distraction

After tracking my browsing, I also became more careful about treating tab switching itself as something negative.

Some work genuinely requires a lot of switching.

When I'm solving a technical problem, for example, I might need to move between code, documentation, an AI tool, testing, search results, and other resources.

I could switch tabs many times while remaining completely engaged with the same problem.

On another occasion, I might switch only a few times but move from my work to social media and lose track of what I was doing.

Those two situations shouldn't necessarily be treated as equivalent.

That's why context became more important to me than simply trying to minimize a number.

With Focus Companion, I can categorize browsing activity according to my own context as Focus, Distraction, or Neutral and look at the patterns that appear over time.

A website doesn't always have the same role either.

Something useful for one task might be irrelevant during another. A site I consider distracting in one context could be necessary for work in another.

The goal isn't to make every number go down or to make a dashboard tell me I had a "good" day.

For me, the useful part is having a clearer picture of what actually happened.

Tracking helped me notice patterns I wasn't looking for

When I started looking at my browsing data, I could have focused entirely on totals.

How much focused time did I have?

How much distraction?

How many times did I switch tabs?

Those numbers can be useful, but the more interesting discoveries came from looking at the circumstances around them.

My distraction wasn't distributed evenly throughout the day.

My tab switching wasn't always caused by distracting websites.

Some unnecessary switches happened because irrelevant work tabs were already open.

Others happened when a task became difficult.

AI introduced a completely different trigger: waiting.

And something as ordinary as background music could create another reason for me to interact with the browser.

Individually, these are small observations.

Together, they changed how I approach my work.

What actually helped me

After 30 days, I didn't come away with an elaborate productivity system.

Most of the things that helped me were small.

I keep only the tabs relevant to my current task open.

Not the ones I'll probably need later. I can save those and return to them when they become relevant.

I pause before opening an unnecessary tab.

When I notice myself wanting to leave the current task, I ask:

> Do I need to open this tab right now?

If the answer is no, I try to stay with what I'm doing.

I stay with the same problem while waiting for AI.

Instead of immediately checking social media, my phone, or beginning another task, I use that time to understand the problem, consider alternatives, challenge my assumptions, or improve the prompt.

I usually avoid background music during focused work.

That's what works for me. If music helps you, choosing a playlist beforehand and leaving it alone might reduce unnecessary switching.

And finally:

I pay more attention to when I'm trying to work.

Knowing that I tend to focus particularly well between 10:00 and 12:00 and again later in the evening gives me useful context. Likewise, recognizing that 14:00 to 15:00 tends to be more difficult helps me understand what I'm seeing instead of assuming every hour should look the same.

The biggest thing I learned after 30 days

Before tracking these patterns, I could easily look at distraction as one broad problem:

I need to focus more.

After 30 days, that feels much less useful.

If I notice myself switching tabs, there are now several questions I can ask.

Is the next tab actually relevant to what I'm doing?

Am I switching because the current task has become difficult?

Am I waiting for AI and automatically looking for stimulation elsewhere?

Do I simply have too many unrelated tabs visible?

Is music pulling part of my attention away?

Am I in one of the periods when I tend to get distracted more easily?

Sometimes none of those things are happening and I genuinely need another tab.

That's fine.

The point isn't to make switching disappear.

It's to understand the difference.

You don't necessarily need to block the distraction first

One of the reasons I built Focus Companion around awareness rather than simply blocking websites is that my own experience with distraction isn't as simple as productive website versus distracting website.

Sometimes the problem is social media.

But sometimes it's documentation for a task I'm not working on yet.

Sometimes it's another productive task.

Sometimes it's waiting for AI.

Sometimes it's music.

And sometimes it's the moment when the problem in front of me becomes difficult and another tab suddenly looks more appealing.

Blocking one website wouldn't tell me any of that.

Seeing the pattern gives me the opportunity to make a more specific change.

For one person, that might mean closing social media.

For someone else, it might mean reducing the number of open tabs.

For me, it might mean keeping my browser limited to the current task, working without music, or staying inside the same problem while AI finishes.

That's what I've found most useful about tracking my browsing.

Not being told whether I was productive.

Becoming more aware of what affects my focus.

Start by noticing one switch

Your patterns probably won't look exactly like mine.

Your strongest focus might happen first thing in the morning. Music might help you concentrate. You might work perfectly well with 30 tabs open. AI waiting time might not distract you at all.

That's why I wouldn't start by copying every change that worked for me.

Start smaller.

The next time you're working and feel the urge to open another tab, stop for a moment.

Ask yourself:

> Do I need to open this tab right now?

If the answer is yes, open it.

If the answer is no, notice what made you want to switch.

You don't have to judge it or immediately block anything.

Just notice it.

Because after tracking my own browsing for 30 days, that's the biggest lesson I've taken away:

Understanding why my attention moves has been much more useful than simply trying to force it to stay still.