Extension Pro
Compliance Score
Use a 0-100 technical score and its factor breakdown to prioritize cookie-consent investigations.
A score helps you choose where to look first. It does not decide whether a website complies with GDPR. ConsentScope's extension score summarizes observed cookie flags, consent timing, classification coverage and privacy-policy discovery for the captured page.
Read the factors beside the number. A missing policy link can reduce the score even when a policy exists on another route. Unknown cookies can affect it because their purpose still needs review. Neither case is equivalent to a confirmed advertising identifier written before consent.
Use comparable scans to track a specific fix. Keep the product version and test conditions with the result; the browser extension and cloud scanner need not use identical scoring models.
What the extension score currently measures
| Factor | Current deduction | How to interpret it |
|---|---|---|
| Cookie flags | 12 points per flag, capped at 60 | Review the observed cookie and its timing |
| Unknown classifications | Up to 25 points, based on the unknown share | Identify purposes that the classifier cannot resolve |
| Policy link discovery | 15 points if no link was found | Check whether discovery missed an existing policy |
| Consent timing | 0-12 points depending on the observed state and delay | Review the scenario; this is not a legal click deadline |
This describes the extension implementation reviewed for this page. The timing factor deducts 10 points when no consent is detected and cookies are present. With measurable consent timing, the current delay bands apply 0, 3, 8 or 12 points. Check the displayed breakdown when versions change rather than relying on an old report's assumptions.
Worked example: why a page received 45
Consider an illustrative scan with four cookies, including one unknown classification and two cookie flags. No consent was detected, and policy discovery found no link. The deductions are 24 for the flags, 6 for classification, 10 for the observed consent state and 15 for the missing link. That leaves 45 out of 100.
This is arithmetic from the model, not a real customer scan. The next task is to investigate the two flagged cookies, identify the unknown one and check the policy route. Adding a policy link could improve the number without fixing the cookie behavior. Report the actual remediation, not just the higher score.
Compare the same scenario before and after a fix
Keep the URL, browser session and observation window consistent. A pre-consent baseline should not be compared with a later scan taken after acceptance. Likewise, a page that failed to load does not become a successful zero-cookie result. Mark that run incomplete and obtain a valid retest.
If the score changes, compare the underlying factors. Was a duplicate tag removed, did the classifier recognize a cookie, or did a policy link become discoverable? Each explanation means something different to the client. The DevTools view can help reconstruct the sequence behind an apparent regression.
Use the score in an agency report without overstating it
Describe it as ConsentScope's technical score for the listed test, followed by the material findings. Include the tested paths and any unresolved classifications. A portfolio average can hide a serious issue on one client site, so keep the per-site findings visible.
For recurring work, combine cloud baselines with manual tests of Reject, partial consent and withdrawal. Use policy analysis when you need to review disclosures. No single number replaces those separate checks.
How it works
Capture the target page under a stated consent scenario.
Open the score and read the individual factors, not only the overall number.
Investigate each affected factor against the underlying cookies and page state.
Repeat the same scenario after the fix and explain the change in the evidence.
Key benefits
Triage a result
Choose the findings that need investigation first.
Explain the number
Use the factor breakdown to show what affected this scan.
Compare a retest
Look for improvement under matching test conditions.
Who is it for
CISOs
Use a technical summary to prioritize browser findings for investigation.
DPOs
Explain score changes alongside the underlying findings and test scope.
Product managers
Define repeatable release checks and review the findings behind each score.
Frequently asked questions
Is 100 a compliance certificate?
Does a slow consent choice make the website unlawful?
Should extension and dashboard scores always match?
Unlock Compliance Score with ConsentScope Pro
Extension Pro provides lifetime access to the paid browser features. Monitor and Agency are separate subscriptions for cloud monitoring. Compare the plans for your workflow.
View Extension Pro