Blocking analytics

The analytics page on the Focus dashboard turns the local tracking data into something you can read at a glance. Use it weekly, not daily — daily fluctuations are mostly noise.

What's on the overview

Top of the page, four metric cards:

• Total blocks (7d) — block events in the last 7 days, with a trend arrow vs the prior week.
• Tracked time (7d) — total browsing time across non-blocked domains.
• Active instances — connected browsers right now.
• Average daily blocks — daily mean with browsing-time context.

Below the cards: charts.

Charts

Daily blocking trend

Line chart of block count per day over the selected window. The shape matters more than any single point:

• Decreasing trend over weeks: you're attempting blocked sites less often. Habit shift in progress.
• Steady high count: the blocks are working — they're firing often, which is the point. Worth checking whether the same sites are responsible (see top blocked).
• Sudden spike: something changed (new stress, new context). Worth thinking about.

Tracked time breakdown

Bar chart of daily browsing time. Useful as a counterweight to block count. If blocks are up and tracked time is down, you're attempting fewer non-productive sessions overall — generally a good sign.

Top blocked sites

Ranked list of the sites that hit blocks most often. Reveals where to focus your custom block list, which categories are working, and which trigger sites need attention.

Hourly distribution

Heatmap of when during the day blocks fire. Often surfaces specific vulnerable windows — late evenings, mid-afternoon slumps, post-meal lulls — that respond to targeted focus modes.

Time range filters

• 7 days — current week, quick check-ins.
• 14 days — two-week view for spotting pattern emergence.
• 30 days — monthly overview for long-term progress.

Don't read shorter windows than 7 days. The signal-to-noise ratio isn't there.

Per-instance filtering

If you have multiple browsers connected, filter the analytics by:

• All instances — aggregate across every browser.
• Single instance — drill into one browser/device.

Useful for finding out which device hosts the most blocks (often the personal laptop in the evenings, etc.).

Week-over-week comparisons

Shown next to the trend metrics:

• Blocks: this week vs last week — context for whether the current period is up or down.
• Tracked time: this week vs last week — same.

A common positive pattern: blocks up, tracked time down — you're attempting fewer non-productive sessions, but the ones you do attempt are getting blocked more reliably.

A pattern to watch: blocks down, tracked time up — either the blocking is loosening, or you've found a way around it. Worth investigating.

Privacy

All analytics are computed from aggregate data only:

• Stored: counts, durations, category-level data.
• Never stored: specific URLs, page content, or browsing details.

If you've disabled analytics in the dashboard, none of these metrics sync — the in-extension popup still shows your local counts, but the dashboard analytics page is empty.

See Tracking and Extension privacy for the data-handling specifics.

Common pitfalls

Using analytics effectively

• Weekly review. Sunday morning, 5 minutes on the analytics page. That's the cadence that catches patterns without creating anxiety.
• Adjust focus modes based on what you see. If a category accounts for most blocks, consider promoting it to a stricter mode. If a specific site dominates "top blocked", add it to your custom block list explicitly so it's blocked even outside the category.
• Celebrate trend improvements. Even small downward trends represent real behavior change. Mark them in your journal.

Next steps

• Tracking — what data feeds the analytics.
• Focus modes — adjust based on patterns.
• Custom block lists — promote top-blocked sites to explicit blocks.