WP Statistics plugin review and common issues

WP Statistics tracks visitors server-side, but certain configurations cause undercounting. Check: (1) caching plugins — if pages are served as full HTML cache without PHP execution, WP Statistics cannot record visits — use the REST API tracking method in WP Statistics Settings → General → Tracker Method, which works with cached pages; (2) CDN configurations that serve pages without hitting your origin server; (3) bots and crawlers are filtered out by WP Statistics by design, which reduces counts compared to tools that count bot traffic.

WP Statistics writes a database record for every page view, generating significant load on high-traffic sites. Mitigation: (1) enable data pruning in WP Statistics → Optimization — set automatic deletion of old records (e.g., keep 12 months of data); (2) add database indexes via the plugin optimization screen; (3) for very high-traffic sites, consider GA4 with cookie consent as the primary analytics tool and use WP Statistics only on sites where GDPR compliance prevents GA4 use.

WP Statistics uses MaxMind GeoIP database to resolve IP addresses to locations. The database must be downloaded and kept updated. Go to WP Statistics → Settings → GeoIP and run the database update. If the update fails, your server may have download restrictions — download the GeoLite2-Country.mmdb file manually from MaxMind (free account required) and upload it to the directory shown in WP Statistics settings.

WP Statistics provides shortcodes for displaying statistics anywhere on your site. Use [wpstatistics stat=”visitors” time=”today”] for today’s visitors, [wpstatistics stat=”pagevisits” time=”total”] for total page views, and [wpstatistics stat=”online”] for current online users. Add these shortcodes to widget areas or page content. A dedicated WP Statistics widget is also available in Appearance → Widgets for placement without shortcodes.

Yes. In WP Statistics → Settings → Privacy, configure exclusions by WordPress user role (e.g., exclude Administrators from being counted), specific IP addresses or ranges, and robots/crawlers. The plugin maintains an automatically updated robots list to filter known bots. For excluding office or agency IPs from client site statistics, add the IP range under the IP Exclusion section.

WP Statistics tracks visitors using a hashed IP address method by default — it does not set tracking cookies. Under GDPR, cookieless server-side tracking based on anonymized IP hashes generally does not require explicit consent, though this depends on data protection interpretation in your country. Consult a data protection advisor for your specific jurisdiction before relying on this for compliance.

WP Statistics is simpler to deploy for GDPR compliance — all data stays on your server, no consent mechanism is needed in most configurations, and there is no third-party data processor relationship. Google Analytics 4, even with consent mode enabled, transfers data to Google servers and requires explicit consent under GDPR in the EU. The trade-off is depth: GA4 provides behavioral analytics, conversion tracking, and audience insights that WP Statistics does not.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.