ConsentLens
Live data · Updated daily

GDPR Compliance Statistics

Aggregate data from 63 website scans — tracking consent violations, third-party trackers, and compliance scores across the web.

Data recalculated daily.

63

Websites scanned

72/100

Avg compliance score

0 = worst · 100 = best

21%

Fire trackers before consent

38%

Fully compliant

How many websites are GDPR compliant?

Compliance level assigned to each scanned website based on the severity and number of issues detected.

Compliant
24 (38%)
Low Risk
23 (37%)
Medium Risk
10 (16%)
High Risk
6 (10%)

What are the most common GDPR violations?

Ranked by the number of scanned websites where each issue was detected.

#ViolationAffected sites
1Long-lived cookies detected24(38%)
2Third-party cookies detected21(33%)
3No cookie consent banner detected12(19%)
4Cookies set before consent12(19%)
5Advertising / remarketing trackers detected11(17%)
6Consent banner missing reject option6(10%)
7Tag manager present — verify all tags respect consent1(2%)
8Google Conversion Linker tracking cookie present — verify consent gating1(2%)
9Twitter Pixel may load before consent is resolved1(2%)
10LinkedIn Ads tracking cookie present — verify consent gating1(2%)

Which trackers are most commonly found?

Number of scanned websites where each third-party tracking technology was detected. Includes trackers found both before and after consent.

Twitter Pixel23 (37%)
Google Analytics21 (33%)
Google Ads9 (14%)
Meta Pixel5 (8%)
Snap Pixel2 (3%)
Segment1 (2%)
Google Tag Manager1 (2%)
Microsoft Clarity1 (2%)
Amplitude1 (2%)
Mixpanel1 (2%)

How are compliance scores distributed?

Each website receives a 0–100 compliance score. A score above 80 indicates good compliance; below 40 indicates significant active violations.

0–19
1 (2%)
20–39
5 (8%)
40–59
10 (16%)
60–79
23 (37%)
80–100
24 (38%)

Scan activity — last 12 weeks

Number of completed website scans per week.

Methodology

What is a scanned website?
A unique domain that has been scanned at least once using the ConsentLens Playwright-based scanner. Statistics reflect the most recently completed scan per domain.
How is the compliance score calculated?
Each website receives a 0–100 score composed of four equally-weighted sub-scores: cookie consent handling, tracking transparency, third-party script management, and consent option availability.
What does 'fires before consent' mean?
Any tracker that sends a data-collection network request (XHR, fetch, beacon, or image pixel) within the first 500ms of page load, before the user has had the opportunity to interact with a consent interface.
Data freshness
Statistics are recalculated from the live database once per day. The timestamp at the top of this page shows when data was last computed.

Based on 63 completed scans.

Scan your website →
Report issue