"4,000 PVs! Let's Go!"

One day, I opened my Cloudflare dashboard.

HTTP Requests: 4,221

My heart skipped a beat. Over 4,000 page views? Seriously? That's amazing. Could this be the first sign of success?

I almost posted "Just hit 4,000 PVs!" on social media. Thank god I investigated before I did.

The Truth Was Brutal

4,221
HTTP Requests (apparent PVs)
3,691
Workers API Requests (bots & APIs)
530
Real User PVs (RUM measurement)

87.4% were API requests.

Cloudflare Workers API requests, bot crawls, health checks — they were all counted as "HTTP Requests." The number of actual humans viewing the site in a browser was 530.

The dream of 4,000 collapsed in an instant.

Why We Get Fooled

The Cloudflare Analytics Trap
Zone HTTP Requests = All HTTP requests (including APIs, bots, and prefetches)
RUM (Real User Monitoring) = Actual page loads by real users in browsers

These are two completely different numbers. Mistake the former for "page views," and you'll be riding a high on numbers 8x larger than reality. And the crash when that high wears off is devastating.

It's a classic trap for indie developers. Skip setting up Google Analytics, glance at your hosting dashboard, and celebrate "PVs are going up!"

Numbers are meaningless unless you understand what they're actually measuring.

This Is the Same "I Thought I Was Counting" Problem Tutors Have

That's when I noticed this has the exact same structure as tutor admin work.

👩‍🏫
"I should have had 15 lessons this month." (checking planner)
📊
Actually counting on the calendar: 12. Three makeup lessons had shifted to a different month. The tally marks in the planner lied.
😱
I almost overcharged the family for three extra lessons……

"Thinking you're counting" is the most dangerous state.

Jotting notes in a planner. Scrolling back through LINE messages. Manually entering data into Excel. They all feel like "keeping records," but they're riddled with gaps.

Thinking you had 4,000 PVs when you had 530, and thinking you taught 15 lessons when you taught 12 — these are the exact same type of failure.

Building a System for Accurate Numbers

Manual Counting

Tally marks in a planner. Transcribe to Excel at month-end. Missed updates for reschedules and cancellations. "Wait, did I teach that week?" — every single month.

Kagemusha System

Just add lessons to Google Calendar. Manage reschedules and cancellations right on the calendar. Auto-tallied at month-end. Zero counting errors.

I solved my PV problem by implementing RUM measurement.

The Kagemusha system solves the lesson-counting problem for tutors.

Let a System Count Your Numbers
Never trust numbers counted by hand. Whether it's page views or lesson counts, they only mean something when measured by a reliable system. With Kagemusha, just add lessons to Google Calendar and your lesson counts, tuition fees, and invoices are generated automatically. ¥500/month. When you consider the risk of losing a family's trust over a counting mistake, it's cheap insurance.

I accepted the reality of 530 PVs. But those 530 are real people who actually visited the site.

An honest 530 beats a fake 4,000.

Look at your numbers honestly. And let an honest system handle your admin work, too.

Still managing tutor attendance manually?

Discover Kagemusha System