고객 지원 문의

이메일로 답장드리며, 보통 이틀 안에 회신합니다.

Google reCAPTCHA가 이 제출을 악용 여부에 대해 확인하며, 이 과정에서 데이터가 Google로 전송됩니다. 스크립트는 이 양식을 열 때만 불러옵니다.

← 전체 글

The number on the badge is not visitors

A recurring question here is why the number printed on the counter image does not match the number in the statistics. Both are correct. They are answers to different questions, and the badge answers the less interesting one.

What each number counts

The badge shows a lifetime total that goes up by one on every counted image load. Somebody who reads three pages on a site moves it by three.

The statistics page keeps a separate daily row with three figures: hits, which matches the badge's definition; visitors, which goes up only the first time a given visitor is seen that day; and bots, kept apart from both.

Across every counter on this service over the last thirty days: 543,937 hits, 262,984 visitors, 62,872 bots. That is 2.07 hits per visitor — a reasonable number to keep in mind when the two figures on a given page look far apart.

The second reason they differ

The badge is a lifetime total. The daily table is not: it starts on 15 July 2025, because that is when it was created.

hits543,937visitors262,984bots62,872

Counter number one is this site's own, running since 2006. Its badge stands at 708,983. Its daily table knows 324,948 hits and 65,269 visitors — everything since July 2025 and nothing before. Neither number is wrong; they cover different spans of time.

What is excluded from both

  • Reloads. A page reopened in a tab that was left open all day is one visit, not forty. Requests marked as repeats do not increment anything.
  • Excluded addresses. Where a counter has been told to ignore a particular range, those visits appear nowhere — not in hits, not in visitors, not in the country or browser lists.
  • Bots, unless the setting is switched on. They are collected either way, so the crawlers stay visible without inflating the badge.

Why the column is named after IP addresses

The database column behind the badge is called ips_all, which reads like "unique addresses" and is not what it holds. It holds hits. The name is left over from an older schema and was never changed, and the field has been read as "visitors" more than once because of it.

Nothing about the counting is wrong. The label on the box is, and a wrong label is quite good at surviving, because everyone who reads it comes away confident. The number the label promises is not missing. The statistics page for the same counter shows visitors and views next to each other, for the same period, each under its own name.

광고