UAU Ready
Descrição
Quando um site na Europa precisa estar em conformidade com o GDPR sem sacrificar a velocidade, o OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts substitui as requisições externas às fontes do Google por uma versão local hospedada no próprio servidor, eliminando a transferência de dados para terceiros. Essa abordagem atende blogs, portfólios e sites institucionais que desejam unir privacidade e performance com suporte a mais de 900 famílias tipográficas, além de oferecer cache inteligente e pré-carregamento para otimizar ainda mais a entrega.
Principais Características do OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts
- Hosteamento local automático
Baixa as fontes do Google para o servidor e as serve a partir do próprio domínio, eliminando requisições externas. - Conformidade total com o GDPR
Nenhum dado do visitante é enviado ao Google, garantindo privacidade desde a primeira visita. - Otimização de cache
Armazena as fontes em cache com headers de expiração, reduzindo o carregamento em páginas seguintes. - Pré-carregamento inteligente
Adicionarel="preload"a cada fonte, carregando-a antes mesmo da interpretação do CSS. - Controle sobre as famílias
Selecione manualmente quais famílias serão hospedadas ou deixe o plugin detectar as utilizadas no tema.
Benefícios do OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts
- Mais velocidade no carregamento
Reduz o número de conexões DNS e evita bloqueios de rede por serviços terceiros. - Privacidade sem complicação
Adequa o site à legislação europeia sem necessidade de plugins extras de consentimento. - Manutenção simplificada
Atualiza automaticamente as fontes baixadas conforme novas versões são lançadas. - Melhor experiência mobile
Fontes servidas localmente carregam de forma consistente mesmo em redes lentas.
Para Quem o OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts é Indicado?
- Sites europeus que precisam de conformidade com o GDPR.
- Blogs e portfólios que utilizam Google Fonts.
- Desenvolvedores que buscam aliar performance à privacidade.
Como Baixar o OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts
O OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts está disponível para download aqui no Ultrapack. Após baixar o arquivo .zip, instale em Plugins > Adicionar Novo > Enviar plugin, selecione o .zip e ative. O painel de configuração aparecerá em Configurações > OMGF PRO, e o arquivo está completo e pronto para instalação imediata.
Ao hospedar as fontes do Google localmente, o OMGF PRO resolve simultaneamente dois gargalos comuns: a dependência externa que atrasa o carregamento e a exposição de dados de navegação a servidores estrangeiros. É a ferramenta certa para sites que priorizam tanto a velocidade quanto a privacidade dos visitantes, sem exigir alterações técnicas no design ou na tipografia já implementada.
Perguntas Frequentes
O plugin OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts é GPL?
Sim. O OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts é distribuído sob a licença GPL (GNU General Public License). Você pode usar, modificar e redistribuir legalmente, em quantos sites quiser.
Posso usar o plugin OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts em mais de um site?
Sim. Você pode instalar o OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts em quantos sites quiser. Só as atualizações automáticas pelo Ultrapack Auto Updater têm limite: de 3 a 80 sites, conforme o plano.
Quanto custa o plugin OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts no Ultrapack?
O OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts sai por R$ 14,90 na compra avulsa, e também está incluído nos planos de assinatura a partir de R$59/mês (VIP I).
O plugin OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts inclui atualizações?
Sim. A versão atual do OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts é a 5.3.1, publicada no Ultrapack em 07/10/2026. Assinantes atualizam direto do painel do WordPress com o UAU (Ultrapack Auto Updater).
O plugin OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts é seguro para baixar e instalar no meu WordPress?
Sim. Cada versão do OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts passa por varredura de malware (ClamAV e regras YARA, no UltraHub) antes de ser publicada.
Quais são os requisitos do plugin OMGF PRO – GDPR/DSVGO Compliant, Faster Google Fonts?
Requer WordPress 6.2 ou superior e PHP 7.2 ou superior. Testado até o WordPress 7.0.
O que mudou nesta versão
Versão 5.3.1
- Fixed: Smart Optimize stored its results for every URL visitors browsed to, so variations of the same page were analyzed and stored separately, e.g. AffiliateWP's referral URLs (/ref/ /), which may contain an affiliate's email address. Results are now stored for the canonical path of the page. Existing results are removed once, so pages are analyzed again.
- Fixed: Smart Optimize results weren't found on sites installed in a subdirectory, or for paths containing percent-encoded characters.
- Fixed: Smart Optimize no longer analyzes 404 pages for administrators either.
- Added: the omgf_pro_smart_optimize_path filter, to normalize the path Smart Optimize stores its results for.
- Security: Smart Optimize only stores results for paths signed by your site, i.e. pages it actually rendered, so its table can't be filled with made-up paths.
Versão 5.3.0
- Added: compatibility with Thrive Leads (and other Thrive products loading forms through Thrive Dashboard): Google Fonts @imported by forms which are loaded asynchronously are now replaced with locally hosted copies.
- Added: Smart Optimize results reported by visitors can only preload font files hosted on this site, OMGF's upload URL, a host the site already loads stylesheets, scripts or fonts from, or a whitelisted host: hosts of preloads reported during an administrator's visit are whitelisted automatically, other hosts are listed on the Dashboard for approval (the stoplight in the admin bar turns blue), and the whitelisted and ignored hosts can be managed below the Smart Optimize option.
- Improved: preloads' and unloads' paths are validated and the number of stored preloads and unused fonts is now limited.
- Improved: font files OMGF couldn't download correctly are reported as an alert (red) in the admin bar, instead of a warning, because OMGF Pro can't fix those. Requires OMGF v6.3.12.
- Security: external stylesheets are fetched over a safe request that rejects internal/private hosts.
- Security: asynchronously loaded Google Fonts stylesheets are only processed during an authorized Auto-Config run.
- Security: only the query string of a Google Fonts stylesheet URL is decoded before it's requested.
- Tested with WP 7.1.
Versão 5.2.11
- Note: this release requires OMGF v6.3.11 or higher. On older versions the clean up below is postponed until OMGF is updated, and Material Icons stylesheets aren't processed until then.
- Security: hardened the detection of Material Icons stylesheets, in line with OMGF v6.3.11.
- Fixed: Magic Fallbacks kept asking to contact support about fonts which never existed, e.g. 'Arial,Helvetica,sans-serif !important', 'var(--tve-font-family,Mulish)' and 'inherit'. Whenever the Google Fonts API returned no fonts for a font family found in a local or inline stylesheet — which is always the case for a font installed with WordPress' Font Library — OMGF Pro < v5.2.9 ran the optimization again with the entire document, instead of that font's @font-face statements. Every font-family declaration in that document was then stored as a font family. This release removes those entries from the Optimized Fonts table, and Magic Fallbacks now ignores any value which can't be the name of a font, instead of reporting it.
Versão 5.2.10
- Note: this release detects stylesheets which were skipped before, so optionally run Save & Optimize once after updating to add them to your cache. Nothing breaks if you don't.
- Fixed: Optimize Local/External Stylesheets skipped any link element written over multiple lines (or with a line break inside its href attribute), while browsers load those just fine. The pattern used to find them couldn't match line breaks, but could run past the > which ends an element. Both are fixed, and line breaks are now stripped from the URL before it's requested, just like browsers do.
- Improved: the classes which collect @import statements (and the one which adds the Material Icons subset) registered their filters once per instance, while they're constructed on every processing run. Because nothing ever removed those filters, they stacked up within a single request, which meant the same @import could be optimized several times over, and the Material Icons subset could be added to the subset list more than once.
- Fixed: @import statements spread over multiple lines weren't detected. CSS allows whitespace (incl. line breaks) after @import and inside url, and a backslash followed by a line break is a line continuation inside a string, but none of those were matched. A raw line break inside the URL is still ignored, because that's an unterminated string, which browsers don't load either.
- Fixed: Smart Optimize (Unused Fonts) could return a blank page when an inline @import statement was fully unloaded. The pattern used to remove that statement removed everything between the first @import and the last occurrence of the stylesheet's URL, and exceeded PCRE's runtime limits on documents larger than ~100KB, in which case the entire document was replaced with nothing (accompanied by a 'preg_replace_callback: Passing null to parameter #3 ($subject)' deprecation notice). Matching is now confined to a single @import statement, and a failed search/replace leaves the document untouched.
- Fixed: Smart Optimize (Unused Fonts) didn't remove any @font-face rules from stylesheets whose fonts are split into subsets. The subset was matched against the font file's URL using a pattern which
- couldn't match the hyphen separating the subset from the font-weight (e.g., source-sans-pro-normal-latin-400.woff2), so no rule ever matched. The subset is now matched against the @font-face rule's
- unicode-range, and only falls back to the filename for rules which don't define one.
- Fixed: Smart Optimize (Unused Fonts) now removes a stylesheet's link element from the HTML entirely when all of its @font-face rules are unloaded, instead of leaving behind a request for an empty stylesheet. Generated stylesheets always start with a header comment, which meant they were never detected as empty. This also fixes the deregistration of fully unloaded Async Stylesheets.
- Fixed: an unused Material Icons stylesheet wasn't removed from the HTML. Its cached URL was looked up in the wrong list, so it was never recognized, and clearing the link element's href attribute left behind a request for the page itself. Its link element is now removed entirely.
Versão 5.2.9
- Fixed: with Magic Fallbacks enabled, the first click on a Replace checkbox checked all corresponding "Don't Load" checkboxes, but left the Replace checkbox itself unchecked.
- Fixed: with Magic Fallbacks enabled, a Replace checkbox stayed disabled after unchecking the Preload checkbox(es) of the corresponding font family.
- Fixed: A corrupted (non-array) Fallback Font Stack option no longer causes a fatal error ('Cannot access offset of type string on string') when opening the Optimize Fonts settings screen.
- Fixed: Magic Fallback aliases were incorrectly stored as font families during Save & Optimize, causing a 'could not find a matching fallback font' notice.
- Fixed: Magic Fallbacks no longer tries to find a fallback for icon fonts (e.g., Material Icons/Symbols) and no longer shows a 'could not find a matching fallback font' notice for them.
- Fixed: Smart Optimize now purges the page cache on taxonomy archives, the homepage and WooCommerce product pages by switching supported caching plugins (LiteSpeed, W3 Total Cache, WP-Optimize, WP Rocket, WP Super Cache) to URL-based purging, so the detection script no longer re-runs on every page load for URLs without a single post-ID.
Notas de versão publicadas pelo desenvolvedor.
Como instalar
Atualização automática: este item é atualizado pelo Ultrapack Auto Updater. Com ele instalado, a versão nova aparece no seu painel como qualquer outra atualização do WordPress (como configurar).
Este Pro é um complemento da versão gratuita. Sozinho ele não funciona.
- No painel do WordPress, vá em Plugins > Adicionar novo, busque o plugin pelo nome no repositório oficial e instale a versão gratuita. Ative.
- Baixe o arquivo
host-google-fonts-pro.zip. - Vá em Plugins > Adicionar novo > Enviar plugin, selecione o arquivo
host-google-fonts-pro.zipe clique em Instalar agora. - Clique em Ativar. As duas versões ficam ativas ao mesmo tempo.
Requisitos: Requer WordPress 6.2 ou superior e PHP 7.2 ou superior. Testado até o WordPress 7.0.
- Desativar a versão gratuita desliga o Pro junto.
Travou em algum passo? Abra um chamado dizendo em qual deles parou.
