PageViews Counter
There are deffinitely different methods for implementing pageview counters. Considering some external service such as Jetpack or Google Analytics is surely a good option, but there may be scenarios where you may want to handle this just by yourself and have everything more under control.
Since it’s very common to utilize some caching mechanism to improve your site’s performance, implementing counter directly on PHP level wouldn’t work reliably as counter would be barely incremeneted due to the caching. Better solution would be to use WordPress way of triggering AJAX requests and increment pageview counters anytime page is loaded, no matter if served from cache or not.
When we start to think on bigger scale though, we find tradional WP AJAX implementation quite resources heavy as well. This plugin uses slightly more complicated method to increase counters, but it’s very lightweight. In a nuthsell, counters are stored ‘outside’ of WordPress ecosystem into some fast storage such as Memcached or Redis. Then there’s implemented re-occuring cron task on WordPress level, which regularly checks for new counters and store its values as postmeta for each respective post.
Plugin utilizes PhpFastCache library which allows to store data into many types of back-ends. See their documentation for more details. This feature allows you to choose any back-end depending on your hosting provider.
This plugin comes preconfigured with file-based storage, which should work on any hosting environment, but for higher traffic sites you may want to consider in-memory storage such as MemcacheD.
Whole principle and idea is described in following article published on my blog.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| m*n*o*i*i*a*.pt | D | Aug 18, 2026 | |
| c*l*i*s*o*t*.com | C | Aug 17, 2026 | |
| s*n*o*5*.com | F | Aug 15, 2026 | |
| c*a*e*a*d*u*h.info | C | Aug 15, 2026 | |
| g*o*r*n*c*.sk (WP 6.7.6) | F | Aug 7, 2026 | |
| l*u*e*i*n.c*m.br (WP 7.0.2) | F | Aug 3, 2026 | |
| b*g*s*a*d*o*s.com | F | Aug 2, 2026 | |
| a*i*l*f*n.com (WP 7.0.2) | C | Jul 31, 2026 | |
| t*e*i*h*l*s.com (WP 7.0.2) | F | Jul 31, 2026 | |
| m*h*q*r*n.com | F | Jul 31, 2026 | |
| t*e*e*d*m.com | F | Jul 30, 2026 | |
| f*l*o*f*l*o*.com | D | Jul 29, 2026 | |
| r*6*.cz | F | Jul 27, 2026 | |
| m*e*u*v*r*u.com | C | Jul 25, 2026 | |
| t*r*s*e*s*o*.org | F | Jul 24, 2026 | |
| a*s*n*l*m*n*a.com | D | Jul 23, 2026 | |
| w*e*l*n*w*o*l*n*.com | C | Jul 22, 2026 | |
| l*r*s*f*a*n.net (WP 7.0.2) | C | Jul 21, 2026 | |
| f*j*o*k*.sk | C | Jul 19, 2026 | |
| g*m*b*i*o*t*u*n*h*t.com | C | Jul 18, 2026 | |
| r*n*r*p*s.com (WP 7.0.1) | C | Jul 18, 2026 | |
| s*o*t*i*n*s*.c*.uk | C | Jul 17, 2026 | |
| e*i*p*.com | F | Jul 15, 2026 | |
| e*r*w*e*l*n*w*.com | C | Jul 15, 2026 | |
| e*r*n*w*2*7.com (WP 7.0.1) | D | Jul 15, 2026 | |
| e*r*-*e*k*y.com | C | Jul 15, 2026 | |
| o*f*c*a*w*s*h*m*u*t*o*s.com | C | Jul 13, 2026 | |
| y*n*i*h*a*g*i*.com (WP 7.0.1) | F | Jul 11, 2026 | |
| w*e*e*s.com (WP 7.0.1) | C | Jul 11, 2026 | |
| t*l*n*a*a*a*i*s*n*a*.com (WP 7.0.1) | F | Jul 11, 2026 | |
| w*e*t*i*g*e*d*i*e*.com (WP 7.0.1) | C | Jul 11, 2026 | |
| h*m*e*s*h*t.com | C | Jul 10, 2026 | |
| t*f*e*o*.com | C | Jul 10, 2026 | |
| m*n*a*o*e*n.com (WP 7.0.1) | D | Jul 10, 2026 | |
| l*v*r*o*l*a*e*t*e*s.com (WP 7.0.1) | C | Jul 9, 2026 | |
| l*v*4*i*e*p*o*.com | D | Jul 9, 2026 | |
| g*y*h*n*w*a*t*.com | F | Jul 7, 2026 | |
| t*e*e*t*a*w*y.c*.uk (WP 7.0) | C | Jul 5, 2026 | |
| t*e*e*t*a*w*y.com (WP 7.0) | C | Jul 5, 2026 |