Scanned on 14 August 2026 at 21:04 UTC
As of , lewebsterlacy.com has a GDPR compliance score of 55/100 with 15 pre-consent tracking violations detected.
Only Privacy Score 100 means full compliance. These violations mean that before you could even click the Cookie Consent banner, this website already collected your personal data and shared it with third parties. Learn why this matters (our blog) →
Who is responsible? The website owner is solely responsible for these violations and in general often benefits monetarily (directly or indirectly) from collecting and sharing your data without your consent.
No consent platform recognised
The site may use a custom or unrecognised banner. This is informational and does not affect the score.
Tracking cookies are used to identify and follow users across websites. Under GDPR, these require explicit consent before being set, but on this website they are active immediately.
Low-severity concerns: external fonts, empty tag containers, WebSocket connections, and third-party storage.
Services and cookies that comply with GDPR requirements. No consent needed.
Pending classification by our team. No impact on your privacy score.
These items are pending classification. No impact on your privacy score.
Most findings on this page are configuration problems, not catastrophes. These plain-language guides explain what each one means and how to fix it, written for website owners rather than lawyers.
All guides live at gdprscanner.eu/guides.
lewebsterlacy.com has a GDPR compliance score of 55/100.
A score between 50 and 79 indicates moderate GDPR compliance issues. Analytics trackers or advertising scripts are likely loading before user consent, which may result in regulatory attention.
3 trackers detected loading before user consent:
Legal basis: This violates GDPR Article 44 and LG München I (Case 3 O 17493/20, 20 January 2022). Loading fonts from external servers transmits visitor IP addresses to third-party servers, often outside the EU. The Munich Regional Court ruled on 20 January 2022 that embedding Google Fonts without consent violates GDPR, awarding €100 in damages per visitor. Self-hosting fonts eliminates this violation entirely.
Legal basis: This violates GDPR Article 44 and LG München I (Case 3 O 17493/20, 20 January 2022). Loading fonts from external servers transmits visitor IP addresses to third-party servers, often outside the EU. The Munich Regional Court ruled on 20 January 2022 that embedding Google Fonts without consent violates GDPR, awarding €100 in damages per visitor. Self-hosting fonts eliminates this violation entirely.
This GDPR compliance scan of lewebsterlacy.com was performed by GDPR Scanner, a pre-consent privacy scanning tool. The scan captures all trackers, cookies, and third-party scripts that load before a user clicks any consent button.
Under GDPR (General Data Protection Regulation), websites must obtain explicit consent before processing personal data. Any tracker or cookie that fires before consent is a potential violation of EU privacy law.
A privacy score of 100/100 means the website loads zero trackers and zero tracking cookies before the user gives consent. This is the standard required by GDPR Article 5(1)(a) and Article 7.
Essential cookies (session management, security tokens) and first-party functional cookies do not incur penalties, as they are covered by the legitimate interest legal basis. See an example: playhth.com scores 100/100.
| Cookie Name | Domain | Type | Service | Duration |
|---|---|---|---|---|
| sbjs_session | .lewebsterlacy.com | 1st party | WooCommerce - The number of page views in this session and the current page path | Session |
| sbjs_current | .lewebsterlacy.com | 1st party | WooCommerce - Traffic origin information for the visitor’s current visit to your store | Session |
| sbjs_migrations | .lewebsterlacy.com | 1st party | WooCommerce - Technical data to help with migrations between different versions of the tracking feature | Session |
| sbjs_current_add | .lewebsterlacy.com | 1st party | WooCommerce - Timestamp, referring URL, and entry page for your visitor’s current visit to your store | Session |
| sbjs_first | .lewebsterlacy.com | 1st party | WooCommerce - Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires) | Session |
| sbjs_udata | .lewebsterlacy.com | 1st party | WooCommerce - Information about the visitor’s user agent, such as IP, the browser, and the device type | Session |
| sbjs_first_add | .lewebsterlacy.com | 1st party | WooCommerce - Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires) | Session |
lewebsterlacy.com has 15 GDPR compliance violations with 3 trackers loading before user consent. This level of non-compliance carries meaningful regulatory risk.
Under GDPR Article 83, supervisory authorities can impose fines of up to €20 million or 4% of annual global turnover, whichever is higher. While fines for consent violations typically range from €10,000 to €500,000, larger organisations have faced fines exceeding €50 million.
Implementation of a properly configured Consent Management Platform (CMP) that blocks all non-essential scripts until consent is obtained is the recommended remediation step.
lewebsterlacy.com scores 55/100 with 15 violation(s) detected. Trackers or cookies were found loading before user consent.
Our scan detected 9 tracker(s) loading before consent, including Google Fonts, Font Awesome, Fonticons.
Yes, 8 cookie(s) were detected before the user interacted with any consent banner.
lewebsterlacy.com has a GDPR compliance score of 55/100 as of 14 August 2026. A score of 100 means no trackers or cookies load before consent. lewebsterlacy.com currently has 15 violation(s) affecting its score.
lewebsterlacy.com should implement a Consent Management Platform (CMP) that blocks all non-essential trackers and cookies until the visitor gives explicit consent. This includes configuring tag managers like Google Tag Manager to use consent-aware triggers, self-hosting external fonts, and auditing all third-party scripts. After making changes, re-scan with GDPR Scanner to verify compliance.