Google Fonts avant consentement ou chargement externe des polices

Pourquoi c'est important

Les requêtes externes de polices peuvent exposer l'adresse IP d'un visiteur à des tiers avant consentement. Le transfert réseau lui-même peut suffire à déclencher un constat.

Comment vérifier manuellement

1. Inspect the Network panel for requests to fonts.googleapis.com or fonts.gstatic.com on first load.
2. Check the page source and CSS bundles for @import or remote font references.
3. Verify whether theme, builder, or plugin settings re-enable hosted fonts after deployment.

Causes typiques

• Theme or page builder loads Google Fonts by default.
• Remote @import remains in CSS even after partial self-hosting.
• Performance plugins aggregate CSS but preserve remote font URLs.

Correction dans GTM

1. Remove any GTM-delivered custom HTML that injects Google Fonts or icon CDNs.
2. Audit marketing landing page tags for embedded font imports.
3. Keep typography assets outside tag-manager delivery unless strictly necessary.

Correction dans WordPress ou les plugins CMP

1. Disable Google Fonts in theme or builder settings and switch to local assets.
2. Use a self-hosting plugin or theme option to download and serve fonts locally.
3. Purge cache and verify the frontend no longer calls Google font endpoints.

Correction générique côté développeur

1. Download required font files and serve them from your own origin or CDN.
2. Replace remote stylesheet imports with local @font-face declarations.
3. Remove fallback components that reintroduce hosted fonts on specific pages.

Comment confirmer que la correction fonctionne

• Reload the page with a clean cache and confirm no Google Fonts requests occur.
• Check multiple templates and breakpoints to ensure no remote font reference remains.
• Run a fresh scan and verify the font-related finding is gone.