Visitor Traffic Real Time Statistics Pro

Melhoria

• Stronger bot filtering: crawlers and automated browsers that run JavaScript but do not call themselves "bot" (GoogleOther, Google-InspectionTool, Chrome-Lighthouse, HeadlessChrome, Puppeteer/Playwright/Selenium, uptime monitors, HTTP libraries, AI crawlers...) are no longer counted. Both the real request User-Agent and the one reported by the page are checked, and automated browsers (navigator.webdriver) are ignored. Real visitors on CUBOT phones are counted again.
• Pages prerendered by the browser are only counted when the visitor actually opens them. Chrome prerenders top Google results, which was inflating "search engine visits".
• Accurate time on site: engaged time is measured in the browser (visible tab + recent interaction) and reported per page view. It replaces the Heartbeat-based duration, which kept counting for idle/background tabs and measured the first-to-last request of an IP over the whole day. Single-page visits are part of the average. Visits recorded before 11.26 show "-" instead of an invented value. The "Engaged" journey filter and the duration sort use the new value.
• "Online now" is kept up to date by a lightweight report every 60 seconds while the visitor's tab is visible (background tabs no longer count as online).
• Clearer traffic sources: each visit is counted once, under the source of its first page (Organic Search, Direct, Referral, Social Media, UTM Traffic). Google visits now appear under Organic Search, and Gmail, Google Docs, Translate and similar links are no longer counted as search engine visits.
• More accurate countries: the visitor IP is taken from Cloudflare/CDN headers first, internal proxy addresses are skipped, "IP:port" values are understood, the city is no longer borrowed from a different country, and the location cache now expires after 30 days.
• Visitors whose IP cannot be determined are no longer counted as a new visitor on every page view.
• Database schema checks (including ALTER TABLE statements) no longer run on every request, only once after an update. The front end no longer loads jQuery and WordPress Heartbeat for visitors, and the visitor IP is no longer printed into the page HTML.