Calculator Inputs
Example Data Table
| Site | Pages Scanned | Early Cookies | Non-Essential Early | Reject Button | Logging | Score | Risk |
|---|---|---|---|---|---|---|---|
| ShopWave.io | 30 | 1 | 0 | Yes | Yes | 92.00 | Low Risk |
| MediaNest.net | 18 | 4 | 2 | No | Yes | 63.50 | Elevated Risk |
| OfferGrid.org | 8 | 6 | 4 | No | No | 38.00 | High Risk |
Formula Used
This checker uses a weighted compliance score. It starts from 100, then subtracts penalties for early cookie activity, missing controls, weak governance, slow blocking, and outdated scanning.
Higher scores indicate stronger consent implementation. Larger penalties reveal where consent controls, timing, or governance need faster remediation.
How to Use This Calculator
- Enter the site name and the number of pages included in your audit.
- Record how many cookies appear before visitor consent is captured.
- Separate non-essential cookies from total early cookie activity.
- Set each control field to match your banner, buttons, links, and logging setup.
- Add the average blocking delay and your rescan interval.
- Submit the form to view the score, penalty table, chart, and export options.
- Use the highest penalties as your immediate optimization priorities.
Frequently Asked Questions
1. What does this calculator evaluate?
It estimates consent readiness by scoring early cookie activity, banner visibility, button availability, logging, regional targeting, withdrawal controls, and review frequency. The result is a weighted compliance score, not a legal determination.
2. Why are non-essential cookies weighted heavily?
Non-essential cookies firing before consent usually signal the most serious implementation gap. They can affect analytics, ad platforms, and profiling scripts, so the scoring model gives them the largest penalty range.
3. Can a high score guarantee compliance?
No. A strong score only indicates better technical alignment with common consent practices. You still need policy review, jurisdiction checks, vendor mapping, and legal validation for your specific business model.
4. What is a good target score?
A score above 90 suggests a mature setup with limited technical gaps. Scores from 75 to 89 usually need smaller adjustments. Anything below 60 should be reviewed quickly.
5. Why does page coverage matter?
Scanning too few pages can hide template-specific scripts, embedded tools, or regional variants. Broader coverage improves confidence that your banner and tag controls behave consistently across the site.
6. How often should I rescan consent behavior?
Monthly is a strong baseline for active marketing sites. Rescan sooner after tag manager changes, CMS releases, new ad tools, A/B tests, or plugin updates that can introduce unexpected cookies.
7. Does the chart help with remediation planning?
Yes. The Plotly chart visualizes which penalty categories contribute the most score loss. That makes it easier to prioritize code fixes, UX updates, and governance tasks in the right order.
8. Can I use this for multiple sites?
Yes. Run the form separately for each domain, subdomain, or regional property. Export the CSV or PDF outputs to compare penalty patterns and track improvements over time.