Google Fonts check: Does your website load Google Fonts?
The Google Fonts check looks everywhere fonts can be loaded from Google servers: in the HTML, in linked CSS files, via the WebFont loader and through embedded maps and videos. Many checks miss the CSS files, although themes often load Google Fonts there via @import.
What gets checked
- Google Fonts in the HTML (link, preload, WebFont loader)
- Google Fonts in up to 10 CSS files (@import, @font-face)
- Pre-connections to Google (preconnect)
- Google Maps and YouTube, which bring their own Google fonts
- Self-hosted fonts
Limits of this check
- The entered page is checked without JavaScript. Fonts that a script loads later only show up if the call is in the HTML.
- Check sub-pages with a different layout, such as a shop or blog, separately.
- The result is a technical assessment, not legal advice.
Every check explained
What each point in the report means, why it matters and how to fix it.
- Google Fonts in the HTML
The HTML loads fonts from Google servers (several places). Every visitor’s IP address goes to Google without consent.
How to fix it: Download the fonts and host them locally. On WordPress, a setting in the theme or page builder (“load Google Fonts locally” / “disable”) often does it.
- Google Fonts in CSS files
The CSS files load Google Fonts (several places), usually via @import in the theme. Many cookie banners don’t block that.
How to fix it: Remove the @import from the CSS file and host the font locally via @font-face. With themes, use a child theme so updates don’t bring it back.
- Pre-connection to Google
The page opens a connection to Google font servers in advance (preconnect). That transmits the IP address too.
How to fix it: Remove the preconnect or dns-prefetch entry for fonts.googleapis.com and fonts.gstatic.com. Local fonts don’t need it.
- Embeds with Google fonts
Embedded maps or videos load without consent and bring their own Google fonts.
How to fix it: Load maps and videos only after a click or consent, for example via a two-click solution in your consent tool.
- Local fonts
No self-hosted font files found. The site probably uses system fonts, which is fine for data protection.
Matching package
from€290
Cookie banner, tracking and embedded services set up properly.
Questions
Why is Google Fonts a problem?
When a page loads fonts from Google servers, the visitor’s IP address goes to Google without consent. A Munich court awarded damages for this on 20 January 2022 (3 O 17493/20), followed by a wave of warning letters in Germany. The question is now before the CJEU (C-654/25).
How do I host Google Fonts locally?
Download the font files, put them on your own server and load them via @font-face. Then remove all references to fonts.googleapis.com and fonts.gstatic.com, including in the theme, page builder and plugins, and run the check again.
More checks
Does AI mention your business?
We ask ChatGPT, Perplexity and Google’s AI Overview the questions your customers would ask and see whether you come up in the answers.
Create an llms.txt for your website
An llms.txt is a file in the root of your website that tells AI systems, in a simple format, which pages matter and what each one covers.
How fast does your website load?
The measurement runs on Google Lighthouse.
What does your website load before consent?
We open your page the way a new visitor would, before clicking anything, and list every external service and cookie that loads.
How well is your website secured?
The test takes a quick look at your website from the outside and checks HTTPS, the certificate, security headers, cookie settings and how up to date the detectable software is: WordPress with plugins, Next.js (for example on Vercel), Astro, jQuery, Bootstrap and Drupal.
Email check: Does your email arrive, and is your domain safe?
The check reads your domain’s DNS records and shows whether your email can be recognised as genuine or ends up in spam, whether someone can forge email in your name and whether similarly spelled domains are registered.
Spam check: Is this email genuine or a scam?
Paste a suspicious email into the box, in any language.
Quick accessibility check
A quick test for the most common barriers that can be found automatically: missing alt texts, unlabelled form fields, blocked zoom and more.