Cookie check: does your website wait for consent?
Type your address. We read your homepage code and list every third party it loads before the visitor has said yes or no: Google Analytics, Meta Pixel, Google Fonts, YouTube, Maps. Then we check whether a cookie banner is there to hold them back.
- No sign-up, full result
- 16 trackers and embeds recognised
- What each finding means for GDPR
Public pages only. We keep the address and the result, never the page content. This is a technical check, not legal advice.
What “before consent” means
GDPR and the ePrivacy rules say that anything on your website that is not strictly needed for it to work must wait until the visitor agrees. That covers analytics, advertising pixels and anything that sends visitor data to another company.
Many sites have a cookie banner, but the trackers load the moment the page opens, before anyone clicks anything. The tool shows you exactly that: what your homepage loads before the visitor has chosen.
How it works
- 1
You enter the address
Of any public page.
- 2
We read the homepage code
Every script, stylesheet, iframe and pixel it asks for, the way a browser receives it.
- 3
We recognise the third parties
16 common trackers, fonts and embeds, and over 20 consent managers.
- 4
You see what loads early
Each finding is marked as waiting for consent or not, with the fix, so you know what to ask of whoever runs your site, or of us.
Why check what loads before consent
It is the first thing inspectors check
Data protection authorities across Europe, Greece's included, check websites for exactly this: trackers that run before the visitor agrees.
Health data raises the stakes
On a doctor's or clinic's site, a pixel that knows which treatment page someone read is handling health data, the most protected category under GDPR.
Most fixes cost nothing
Hosting fonts locally, swapping a YouTube embed or setting Consent Mode takes hours, not a new website.
Three things we look for on your homepage
Everything that sends your visitors' data to another company counts. These are the ones we find on almost every small business website.
Analytics and ads
Tools that measure and target visitors.
- Google Analytics and Tag Manager
- Meta, TikTok, LinkedIn and Google Ads pixels
- Hotjar, Clarity, Yandex
Fonts and embeds
Things that look harmless but call Google or Meta.
- Google Fonts from Google's servers
- YouTube, Vimeo and Google Maps
- reCAPTCHA, Facebook plugins, chat widgets
Consent
Whether anything on the page can hold them back.
- Over 20 consent managers (Cookiebot, CookieYes, Complianz…)
- Google Consent Mode
- A link to a privacy or cookie policy
Before you press Check
I have a cookie banner. Why does the result say “needs a closer look”?
Because the trackers are still written into the page code. Some consent managers block them as the page runs, others only show a banner and block nothing. From the code alone we can't tell which, so we ask you to confirm: open the site in a private window, reject cookies, and see if Google or Facebook still get called in the browser's developer tools (Network tab).
Are Google Fonts really a GDPR problem?
Loading them from Google's servers sends the visitor's IP address to Google, without consent. In 2022 a court in Munich ordered a site owner to pay damages to a visitor over exactly this. The fix is simple and free: download the fonts and serve them from your own server. Nothing changes visually.
Is this a legal opinion?
No. It is a technical check of what your homepage loads. It shows you where the usual problems are; a lawyer or your data protection officer has the final word on compliance.
Do you check other pages too?
Only the homepage, which is where most trackers are installed. For SEO, speed and visibility to AI assistants there is the free website check, which covers 30 points.Free website check
Want us to fix it?
The websites we build load nothing before consent, with fonts on our own servers and analytics that respect the visitor's choice. Send us your result and we will tell you what your site needs.