OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy. vs Include Sitename in Search Results

OMGF can be downloaded for free without any paid subscription from the official WordPress repository. Trusted by 300,000+ WordPress sites. The original Google Fonts self-hosting plugin. OMGF removes the connection between your site and Google’s font servers, eliminating the DNS lookups and render-blocking requests that slow down LCP and TTFB — while making your site GDPR/DSGVO-compliant in the process. German courts have ruled that loading Google Fonts directly violates GDPR, since visitor IPs get logged by Google. OMGF closes that gap entirely: nothing leaves your server. Install it and it works immediately. No setup required, though there’s plenty to fine-tune if you want to. Detection, Out of the Box OMGF scans your site for Google Fonts, Bunny Fonts (fonts.bunny.net), and Jetpack CDN (fonts-api.wp.com) and downloads them to your own server automatically. It even automatically detects and optimizes Google Fonts loaded by Elementor. Free Features Resource hints cleanup — Strips leftover preconnect, dns-prefetch, and preload hints pointing at fonts.googleapis.com and fonts.gstatic.com — dead weight once your fonts are self-hosted. font-display control — Force font-display: swap (or block, fallback, optional, auto) on your Google Fonts, fixing “Ensure text remains visible during webfont load” in Lighthouse and PageSpeed Insights. Performance Checker — Keeps an eye on your setup and flags what’s costing you points: unused subsets, unused weights, missing preloads above the fold, and layout shift from fonts loading late. Google Fonts checker — Pings you when a theme or plugin update introduces new Google Fonts that haven’t been processed yet. Manual control — Globally unload font families or weights you don’t need. Preload the ones that matter above the fold. Integrates with your stack — OMGF works alongside the optimization plugins and page builders you’re already running, including Autoptimize, FlyingPress, Kinsta, LiteSpeed Cache, SiteGround Speed Optimizer, W3 Total Cache, WP Fastest Cache, WP-Optimize, WP Rocket, WP Super Cache, Elementor, Divi, Beaver Builder, Bricks, Oxygen, and Visual Composer. OMGF Pro Where the free version covers the fundamentals, Pro removes the manual work entirely. Smart Optimize — Measures, on real visitor pageviews, exactly which fonts, subsets, and weights get used above the fold. Preloads what matters, strips what doesn’t. No configuration, no guessing — just measured results. Magic Fallbacks — Generates system font fallbacks mathematically tuned to match each Google Font’s real metrics (size-adjust, ascent-override), so text doesn’t jump around while fonts load. Zero CLS, calculated automatically per font. Deeper detection — Pro reaches fonts the free version and competitors don’t touch: – Inline blocks with @font-face or @import – Local and externally hosted stylesheets using @import – Web Font Loader (webfont.js) – Async, JS-injected Google Fonts loaded at runtime – WordPress’s Font Manager (or Font Library, since WP 7.0) – Variable Fonts (fonts.googleapis.com/css2) – Material Icons Global font-display — Extends font-display control to every font on your site, not just Google Fonts. Everything else: – Automatic Multisite and WPML support – Serve fonts and stylesheets from your own CDN or custom path – Replace font families with system fonts entirely – Whitelabel stylesheets — strip OMGF branding and comments for smaller file sizes – Developer Mode for safely migrating between dev, staging, and production Get OMGF Pro → | Documentation | Tested Plugins & Themes

This plugin adds the JSON-LD schema.org markup for including the Site Name in Search Results on the homepage. This new feature was presented on the Official Google Webmaster Central Blog (Thursday, April 16, 2015 ). There is more info on the Google Developers Website. Use structured data markup on your public website to indicate the preferred name you want Google to display in Search results. You can also provide more than one possible name for your site, and let Google Search algorithms choose between them. Once Google has crawled and indexed the updated page, we can use the provided name in Search results as shown in the screenshot. If you use WordPress SEO by Yoast version 1.6 or newer, you don’t need to use this plugin, as this feature has been included in the version 1.6 update. There is more information in the FAQ section of the plugin. What can I do with this plugin? This plugin adds the JSON-LD schema.org markup for including the Site Name in Search Results on the homepage. After activating the plugin you have to configure the Name you want Google to display in your search results instead of the domain name. When Google next crawls your page, its indexing algorithms will process the site name specified by your markup and make it eligible to be used in Search results. Note: It can take some time before you see a change to the presentation of your site in Search results. Also, Google’s algorithms might choose not to use the name you provided, or not might choose to show the domain name instead. INCLUDE SITENAME IN SEARCH RESULTS in your Language! This first release is avaliable in English and Spanish. In the languages folder we have included the necessary files to translate this plugin. If you would like the plugin in your language and you’re good at translating, please drop us a line at Contact us. Further Reading You can access the description of the plugin in Spanish at: Include Sitename in Search Results en castellano. Contact For further information please send us an email. Translating WordPress Plugins The steps involved in translating a plugin are: Run a tool over the code to produce a POT file (Portable Object Template), simply a list of all localizable text. Our plugins allready havae this POT file in the /languages/ folder. Use a plain text editor or a special localization tool to generate a translation for each piece of text. This produces a PO file (Portable Object). The only difference between a POT and PO file is that the PO file contains translations. Compile the PO file to produce a MO file (Machine Object), which can then be used in the theme or plugin. In order to translate a plugin you will need a special software tool like poEdit, which is a cross-platform graphical tool that is available for Windows, Linux, and Mac OS X. The naming of your PO and MO files is very important and must match the desired locale. The naming convention is: language_COUNTRY.po and plugins have an additional naming convention whereby the plugin name is added to the filename: pluginname-fr_FR.po That is, the plugin name name must be the language code followed by an underscore, followed by a code for the country (in uppercase). If the encoding of the file is not UTF-8 then the encoding must be specified. For example: en_US – US English en_UK – UK English es_ES – Spanish from Spain fr_FR – French from France zh_CN – Simplified Chinese A list of language codes can be found here, and country codes can be found here. A full list of encoding names can also be found at IANA.