Every visitor you're missing. Every leak you're guessing at. Every fix, priced.
One script replaces GA4, Hotjar and a per-page CRO consultant — and shows you the 25-40% of visitors GA4 silently drops. Same login. Same bill.
EU-hosted · cookieless · no Google, no Meta, no tracking pixels
One platform that does the work of three.
The audit is the front door. Inside, three layers run together — each replacing a tool you already pay for.
HowsMyPage Analytics
Cookieless. EU-hosted. The 93–97% of visitors GA4 silently drops, captured and priced.
Watch Visitors
Recordings, heatmaps and visitor journeys with the friction already auto-tagged.
The CRO Brain
19 page-type playbooks. Every fix priced in dollars. Verified after you ship it.
GA4 tells you what 70% of your visitors did. We show you the other 30 — and what they were worth.
See your real traffic
GA4 is a sieve. Brave blocks it, Safari truncates it, ad-blockers strip it on every request. You optimise against a sample, not your audience.
Pageviews, sessions, referrers and OS / device / country down to city. Bot detection that does not need a third-party domain. IP anonymisation by default.
Catch the performance hit before Google does
If your page slows down, your ranking slips a week later and your conversions slip the week after that. Most teams find out from a quarterly report.
Core Web Vitals tracked on every real visit — LCP, INP, CLS, FCP, TTFB — rolled up to p75 mobile and desktop, so you see what Google sees.
Track what people actually do
Pageviews are the smallest story. The real story is the click, the scroll, the form abandon — the thing the visitor did on the way to nothing.
Custom events on any element. Goals with wildcards across URL patterns. Funnels built from the events you already fire — no second tag manager.
Tie behaviour to revenue
Knowing 8% of visitors clicked the button is half a sentence. Knowing they spent €14,300 last week is the rest of it.
Revenue tracking with multi-currency support. UTM analysis across every campaign. Per-source LTV and per-page contribution — not a guess from last-click attribution.
Build the view you actually want
Default dashboards never quite answer the question you have at 9am on Monday. You spend an hour rebuilding the same view every week.
Boards you arrange yourself, segments saved per-team, date-range comparison built in. Filter by source, device, campaign, country — nine ways at once if you want.
Share without leaking
The number your CEO sees should not depend on which spreadsheet your analyst opened. And it should not be re-built from raw API calls every week.
Teams and roles built in. A custom CNAME on Growth and up — analytics.yourcompany.com — so the tracker is invisible to ad-blockers. A REST API for the rest.
"metric": "pageviews",
"range": "30d",
"value": 184230
}
You don't need more recordings. You need them already watched.
Heatmaps that price the cold zones
Most heatmaps are wallpaper. They look good in a deck and tell you nothing about what to fix tomorrow.
Click, scroll and movement heatmaps for every monitored page. Desktop and phone, side by side. A cold zone is not a curiosity — it carries the dollar value of the visitor who never reached it.
Recordings that watch themselves
A pile of session recordings is a chore the size of a Sunday. Half are bots, a quarter are bounces, the useful ones are buried.
Every session is auto-tagged on the way in: rage clicks, dead clicks, U-turns, sudden idles, reached-checkout, abandoned-form. Jump to the second the visitor gave up.
Journeys that show the cliff
A funnel is a guess about the path. A journey is the path. They are not the same thing.
Real visitor journeys, ranked. The most common paths, the most expensive paths, and the page where most journeys collapse. Compare paths that converted with paths that didn't.
Funnels priced step by step
Knowing the funnel leaks 33% somewhere is not a plan. Knowing it leaks €1,840 a month at the cart step is.
Multi-step funnels you build from the events you already track. Every drop carries a monthly dollar tag, sourced from your real visitor count and the benchmark lift for the fix.
An audit isn't a feature. It's the reason the other two layers exist.
19 page-type playbooks
A generic CRO checklist treats every page the same. A homepage is not a product page is not a checkout, and the things that move them are not the same things.
We auto-detect the page type and run the playbook that fits it. Each playbook is a decade of consulting work compressed into a deterministic checklist with dollar weights per finding.
AI fusion — raw data, plain finding
A heatmap is data. A funnel is data. A Core Web Vitals chart is data. None of them is a sentence that tells you what to fix.
The CRO Brain reads the heatmap, the recordings, the funnel and the audit as one diagnosis. It writes the finding in plain English, with the playbook it came from and the dollar value it is worth.
Click density: 0.4 / sq-cm above fold.
INP: 412ms p75 mobile.
Bounce: 71% from Google ads.
Dollar-ranked findings
A list of thirty problems is paralysing. A list of three, with monthly figures attached, is a plan you can ship before Friday.
Every finding carries a monthly dollar estimate computed from your real visitor count and the benchmark lift for the fix. The list is sorted by money, not by severity colour.
Verify the fix — not just ship it
Most teams ship a fix and never close the loop. The next snapshot is six months out and by then the team has changed four other things.
Re-run the audit the moment you ship. The CRO Brain re-measures the funnel and returns a confidence-scored verdict — the fix worked, didn't move the needle, or made it worse.
Find the leak
Make the change
Prove it worked
Competitor benchmarking
Knowing your page is doing okay is not the same as knowing it is doing okay against the page winning your search.
Up to five competitors per page (Growth and up). We audit them on the same playbook and surface what they are doing that you aren't — with the dollar value of the gap, not a generic "you should add testimonials".
Seven bills, one tool.
What a typical CRO and analytics stack looks like — and what HowsMyPage on the Growth plan ($79/mo) replaces it with.
Recordings + heatmaps
Free analytics
Privacy analytics
Product analytics
Consultant report
Looker / Metabase / sheets
Three buyers, one tool.
Solo founder
Ships the site themselves
You came for a free audit because the homepage is leaking and you can't afford a $400 consultant report. You stayed because the audit kept being right, and the platform reads the heatmaps for you when you're a sample size of one.
In-house marketer
Owns conversion, defends every test
You came for the funnel evaluation because your CFO asked why the LinkedIn paid budget isn't pulling. You stayed because every finding lands with a dollar number you can defend in the budget review.
Agency owner
Manages a book of client sites
You came because three clients asked for the same audit in one week and you don't have time to write three reports. You stayed for the cross-site dashboards and the white-label exports — one bill, your branding, every client.
The questions buyers ask before they upgrade.
Why isn't A/B split-testing in this list?
Deliberately. A/B test execution requires injecting a second script that swaps content on your real visitors — which slows the page, fights your CSP, and tends to corrupt the very recordings and heatmaps we use to diagnose the page. We do the upstream half (find the change worth testing, price it) and the downstream half (verify it worked after you ship). The actual swap belongs in your CMS, your CDN, or a dedicated experimentation tool — not bolted onto your analytics script.
How does revenue tracking work without a checkout integration?
You fire a single revenue event from your existing thank-you page or checkout webhook — the value, the currency, and the order ID. We attribute that order back to the session, source, campaign and page sequence we already captured. No app to install, no Stripe webhook to set up if you don't want to.
Can I export to a data warehouse?
Yes. Full REST API on every plan and a daily CSV / Parquet export on Pro and up. Pipe it to BigQuery, Snowflake, ClickHouse or whatever you already pay for — the schema is documented and stable.
How does HowsMyPage handle single-page apps?
Natively. The script listens for history-API changes and re-fires pageview events for every client-side route, with the title and URL your router set. No manual route hooks, no double counting on initial load.
What's the difference between Goals and Funnels?
A Goal is a single number that should go up — one event, one threshold, one chart. A Funnel is a sequence of events — view page, add to cart, reach checkout, purchase — and we tell you where each step leaks and what each leak is worth in dollars. Goals answer "is the thing happening more often?" Funnels answer "where in the path are we losing the money?"
Do I need to install separate scripts for heatmaps and analytics?
No. One script does all of it — analytics, heatmaps, recordings, journeys, funnels and the audit. One tag, one privacy policy line, one network round trip. The script is small, async, and loads after your content paints.
How is Core Web Vitals data collected without slowing the page?
We use the browser's built-in PerformanceObserver and the same RUM measurements Chrome's own Lighthouse uses, sampled on every real visit. Nothing extra is loaded for the measurement — we read what the browser already tracks. The CWV numbers you see are p75 mobile, the same cut Google uses for ranking.
What happens to my data if I cancel?
You keep read access to your reports for 90 days after the last billing date. Bulk export via the API or the daily CSV file is available the entire time. After 90 days the raw events are deleted; the audit reports keep a permanent link so old links still resolve.
Is the AI audit deterministic — will I get the same finding twice?
For the same page, the same visitor data and the same playbook version, yes. The audit is a deterministic checklist with dollar weights, not a free-form language model riff. What can change between two runs is the underlying visitor data — if your traffic shifts, the dollar values shift with it. We pin the playbook version per audit so a re-run can be compared to a prior run.
Can I run this alongside GA4 during a transition?
Yes, and most customers do for the first month. Drop our snippet in and keep GA4 running. After a week, compare the two visitor counts — you'll see the 25-40% of visitors GA4 was missing with your own eyes. Once you trust the number, you pull GA4 at your own pace. The two scripts do not conflict.
You could know exactly what is costing you customers.
It is free, it needs no account, and it takes about a minute. There is no good reason to let the page keep leaking another week — worst case, you learn it is in good shape.
No account · no card · one free audit every 24 hours