Yes. The core visitor and pageview tables are available in the free plugin, so SleekView can read all the data WP Statistics already collects, including referrers, country detection, and per-page views. The premium add-ons (like Mini Chart, REST API) add more functionality but the core analytics data is fully accessible without them.

No. SleekView only queries when you open a table, and queries are paginated against the existing WP Statistics indexes. The wp_statistics tables are already indexed for the dashboard widgets, so the same indexes serve SleekView's grids. Front-end performance is completely unaffected because the analytics tracking continues to run through WP Statistics's normal collection paths.

Yes. Any saved view exports cleanly to CSV with the columns and filters you have configured. Useful for sharing a monthly editorial report with the content team, handing a country breakdown to a partnerships team, or archiving a quarterly performance snapshot for stakeholder reporting.

Yes. Each subsite has its own wp_statistics tables (with the appropriate table prefix), and SleekView respects that scoping. Views show only the data for the current site, which matches how WP Statistics itself behaves on multisite. Network admins can switch between sites and each one renders its own analytics independently.

Yes. Grouping pulls together pageviews and visitors per author, category, post type, or any custom taxonomy. Editorial leads get author leaderboards, content marketers get category-level traffic distribution, and ops teams get post-type breakdowns for capacity planning. The grouping happens in the query itself, so it stays performant on large datasets.

Yes. SleekView reads from both the granular tables (visitor, pages, visit) and the daily Summary Totals tables introduced in WP Statistics 14.16. Summary Totals make month-over-month and year-over-year reports fast even on busy sites because the aggregation is precomputed. SleekView automatically uses the Summary Totals when the date range matches what they cover, and falls back to granular tables when more detail is needed.

Yes. The visitor table updates as WP Statistics tracks visits, and SleekView reads from it directly. Build a view of visits in the last hour, sort by timestamp descending, and watch new entries appear when you refresh. Useful during a launch when the team wants to see traffic landing in real time without waiting for a dashboard widget refresh.

Yes. WP Statistics has options to anonymize IPs, exclude logged-in users from tracking, and hash visitor identifiers. Those settings continue to apply because SleekView reads what WP Statistics has stored, not what raw visitor data would have been. If your privacy settings exclude logged-in admins, the analytics views simply do not show those visits, exactly as configured.