Weblix Analytics – Real-Time Stats & Visitor Counter
by Vahid Behnam 0 (0 reviews)

Weblix Analytics – Real-Time Stats & Visitor Counter

Real-time WordPress analytics: live visitors, pageviews, traffic sources, bots and goals. Privacy-first, self-hosted, no external scripts.

Weblix Analytics ranks #18,275 among WordPress.org plugins with 70+ active installations, is #460 of 1,994 in the Analytics category, and was last updated Sep 17, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.1
v3.2.2 Current Version v3.2.2
Updated 5 days ago Last Update on 17 Sep, 2026
Refreshed 9 hours ago Last Refreshed on
#460 of 1,994 in Analytics Top 25% by installs Downloads -57% this week Actively maintained
View on WordPress.org
Rank
#18,275
+169 this week
Active Installs
70+
-18.6%
KW Avg Position
38
1 worse
Downloads
1.9K
+12 today
Support Resolved
0%
No change
Rating
0%
Review 0 out of 5
0 (0 reviews)

Next Milestone 80

Total Progress 60%
70+ 80+
849
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 4 more installs to reach 80+

Rank Changes

17,824 18,801 19,779 20,757 21,734 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026
17,753 18,883 20,014 21,144 22,274 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026
Current #18,275
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 20 30 40 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026
0 100 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0
0 reviews
Overall 0%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Weblix Analytics – Real-Time Stats & Visitor Counter

No. The tracker sends one small deferred request per page view and has zero impact on page load time. Dashboard aggregation happens in WP-Cron, not on page loads.
Yes — a self-hosted one. Weblix reports the same core numbers site owners actually use (visitors, page views, views-per-visitor, traffic sources, landing/exit pages, engagement rate) plus bot detection, without Google accounts, cookies, consent-banner burdens for basic stats, or any data leaving your server.
Since 3.2.1 a page view is one counted view per visitor identity (IP + browser profile) per URL per 90 seconds — the same shape as mainstream analytics. Reload and F5 bursts inside 90 seconds collapse into one view; a genuine second look after that counts again. People sharing one carrier-grade NAT IP (common on mobile networks) count separately, because the browser is part of the identity. Prerendered (hover-prefetched) pages never count until they are actually opened, and back/forward cache restores count as the real views they are.
Yes, by design. Since 3.0 there is no rotating token inside page HTML: tracker requests are validated by same-origin plus rate limits, so a page cached for days still counts its visitors correctly. The script URL also carries a version parameter so CDNs refresh it after updates. The same protection now covers every dashboard number: all live reads travel as POST with no-store headers, so nothing between the browser and the server may store them, and the server-side snapshots are freshness-stamped so a stale or damaged cache row is rebuilt instead of replayed.
Yes. The root cause was inside the plugin's own storage, not the CDN: when a database-optimization tool deletes the internal expiry marker of a WordPress transient, WordPress silently serves that snapshot forever. Weblix now stamps every live cache with a write time and serves it only while provably fresh — a damaged row is rebuilt automatically on the first request after updating, with no purge and no manual step. If you ever want an instant manual reset, Diagnostics → "Run Cleanup Now" flushes every live cache in one click.
Only the roles you explicitly allow. The Statistics Visibility option (first card in Settings) picks which roles can open the console, see the dashboard widget or the admin bar status — administrators only by default. Roles without permission lose every surface at once and their data requests are rejected server-side; administrators can never be locked out, and Settings and Diagnostics always stay administrator-only.
On every admin screen — and on the site's own pages while you are logged in — the WordPress admin bar carries two live indicators: the current online-visitor count and an insights bell that opens the same smart-notes panel as the console. Wording follows your profile language, both refresh at exactly the Dashboard Refresh interval from Settings, polling pauses in hidden tabs, and both stay hidden on mobile where the admin bar has no room.
Yes. Settings → Dashboard Refresh (10–60 seconds) is the single source of truth: the realtime console, the admin-bar counter and the dashboard widget all follow it. High-traffic sites should pick a higher value — counting accuracy never depends on it, only how fresh the numbers feel.
Yes. It accepts only same-origin requests (Origin/Referer must match your site), applies per-IP rate limits, and never embeds an expiring token in page HTML — which is exactly what keeps counting working behind page cache. An optional hourly HMAC token adds a bonus trust signal when present. Internally: prepared SQL everywhere, escaped output, and nonce + capability checks on every admin action.
Weblix registers crawler UA bypass rules with WP Rocket and LiteSpeed automatically, and marks bot renders as non-cacheable, letting crawlers reach PHP where they are tracked server-side. If a CDN serves HTML entirely from the edge (e.g. Cloudflare "Cache Everything"), PHP cannot run from inside WordPress — add an edge rule for known crawler user-agents. The Diagnostics page detects these situations and tells you plainly, and the Tracking Self-Test verifies your setup end-to-end.

Sign In / Register

You need to sign in or register to use this feature.