Point it at your site.
We read your homepage and sitemap, no signup needed. You get your stack, your site type, your indexed page count, a range of monthly visits and the weight of the tracking code your homepage loads, cookie banner included. Takes seconds.
- Detect your stack + site type
- Count indexed pages from your sitemap
- Estimate your monthly sessions
Every module combination has its measured size.
The install guides show where the script goes in your stack.
See the install guides →- Stack and site type
We read your homepage HTML and look for the marks each framework and each kind of site leaves.
- Indexed pages
We count the URLs in your sitemap.xml, or in the sitemaps its index links to.
- Traffic
A range of monthly visits from that page count. It is an order-of-magnitude estimate, not a measurement.
- Depth
How many pages a visit usually reads on a site like yours. It comes from your site type, not from your traffic.
- Trackers and banner
We load your homepage in a real browser without accepting anything and measure, gzipped, every analytics, ad, session recording, tag manager and cookie banner script it loads. Scripts that load only after consent are not counted.
How to read it
The stack and site type come from your HTML, so they are as reliable as the marks your framework leaves. The traffic range is an order of magnitude from your page count: use it to pick a plan, not as a figure.
The tracker weight is a measurement: it is what a visitor downloads before accepting anything. We group it by kind of script, and whatever loads after consent is left out, so your real figure can be higher.
Which modules you load is your call at install time, and the gzipped size of every combination is measured, never summed. Why that weight matters is in script size and Core Web Vitals.
Ask for a place in the beta.
Anyone can join the list. The accounts we pick get Pro free for the whole beta.