Page Visits Counter – Lite
View on WordPress.orgScores higher than 50% of indexed plugins
About
Display number of visits for each page in admin dashboard and browser developer-tool/console. Doesn't count page refresh as a new visit...
Security History
What It Does
Page Visits Counter Lite records each page view on your WordPress site and surfaces the totals inside the admin dashboard as well as in your browser developer console via an exposed JavaScript object. It includes basic deduplication so a simple refresh does not inflate the count as a fresh visit. The plugin is positioned primarily as a lightweight diagnostic and engagement-tracking tool rather than a full analytics suite.
Who It's For
This plugin fits solo content creators, bloggers, and small site owners who want a quick at-a-glance view of per-page popularity without connecting to Google Analytics or installing a heavier stats plugin. It is also handy for developers and theme builders who want to inspect view counts in the browser console while iterating on a site. Agencies running small client portfolios who need a no-fuss counter will find it useful as well.
Who Should Skip It
If you already use Google Analytics, Matomo, Plausible, or any server-side analytics tool, this plugin is redundant and adds an extra database write per request for data you are already capturing. Larger publishers and e-commerce sites that need segmentation, referrer data, heatmaps, or event tracking should look elsewhere.
The Bottom Line
Page Visits Counter Lite does one specific thing and does it with a tiny footprint, scoring 76.07 out of 100 on PluginCheck. It is a sensible pick for lightweight, on-server view tracking but is clearly outclassed as a serious analytics tool. Treat it as a developer aid or a minimal counter, not a replacement for real analytics.
Related Plugins
Pick WebberZone Top 10 when you want to display popular-post widgets across your site, not just inspect counts in the backend.
Choose SRS Simple Hits Counter if you want a public-facing hits badge on each post rather than an internal developer diagnostic.