Google Fonts înainte de consimțământ sau încărcare externă de fonturi

De ce contează

Cererile externe pentru fonturi pot expune adresa IP a vizitatorului către terți înainte de consimțământ. Simplul transfer de rețea poate fi suficient pentru a genera un finding.

Cum verificați manual

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.

Cauze tipice

• 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.

Remediere în 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.

Remediere în WordPress sau pluginuri 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.

Remediere generică pentru dezvoltatori

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.

Cum confirmați că remedierea funcționează

• 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.