ergonet

Ergonet Cache for WordPress is a free plugin developed by Ergonet srl, an Italian hosting company, to drastically improve the performance of a WordPress website by using a server-side page caching system (NGINX Cache or Varnish Cache).
<h3>BENEFITS</h3>
Using a server-side caching system increases your WordPress site’s performance by a minimum of 30% and up to 70%. Keep in mind that the actual improvement will also depend on your overall website optimization strategy.
<h3>WHAT IS PAGE CACHE AND HOW DOES IT WORK?</h3>
Page cache speeds up your website by storing the entire HTML of web pages directly on the web server, instantly serving them to visitors without needing to query the PHP server or the database again. Depending on your hosting plan, you can enable NGINX page cache (Equilibrio plan) or advanced RAM-based Varnish page cache (Progresso and Successo plans).
<h3>COMPATIBILITY</h3>
The Ergonet Cache plugin is compatible with all other website caching and optimization plugins, such as WP Rocket, W3 Total Cache, WO Optimize, etc. 
The Ergonet Cache plugin functions solely as a communication layer between WordPress and the cache system (Varnish or NGINX) installed on the WordPress hosting platform (any plan) and dedicated cloud hosting (Solo and Multidomain plans) offered by Ergonet, available for purchase at this link: https://www.ergonet.it/hosting/hosting-wordpress-valore 
A fundamental requirement for the plugin to work is enabling the caching system from the WebPanel (Ergonet client area available at https://webpanel.ergonet.it) by the user who purchased the shared or dedicated cloud hosting service.
<h3>HOW THE PLUGIN WORKS</h3>
Once the caching system is enabled from the Ergonet WebPanel and the Ergonet Cache plugin is installed and activated, it will work without any additional configuration. 
Cache resource updates 
Each time the webmaster updates a post or page, the plugin installed in WordPress will automatically delete the old cached version to prevent users from seeing outdated content. 
At the same time, the homepage cache will also be cleared to reflect any new articles available on it. 
Cache resource deletion 
Thanks to the automatic update and removal functionality, there is no need to manually clear the cache. Moreover, forcibly clearing the entire cache is discouraged, as it would remove all previously stored resources (pages, articles, etc.) that had been frequently accessed. 
On websites with a large amount of content, a full cache purge could also cause significant slowdowns due to WordPress needing to regenerate all requested pages or articles from scratch.
<h3>WHAT IS NOT CACHED</h3>
To ensure the plugin works efficiently, some resources and specific HTTP calls are never cached. These include:
<ul>
<li>Any page, article/resource visited by a logged-in user.</li>
<li>Any page, article/resource where a no-cache header or similar is set.</li>
<li>All requests made to the WordPress backend.</li>
<li>All data submission requests (e.g., registration forms, contact forms, comments, etc.)</li>
</ul>
<h3>HOW TO CHECK IF CACHING IS WORKING</h3>
The server-side cache system sets specific HTTP headers indicating whether the requested resource (link) is cached or not. To verify if your website is using the cache correctly, you must check for these HTTP headers. 
It’s essential to ensure you are logged out of the WordPress site you’re checking, as well as from any other WordPress site open in other browser tabs. The first step is therefore to log out from the WordPress admin area. 
Open the developer tools based on your browser:
For Firefox: Menu → Browser Tools → Browser Console
For Chrome: View → Developer Options → Developer Tools
Once the developer tools are open:
Select the “Network” tab 
In Firefox, choose the “HTML” sub-tab, in Chrome, choose “Doc” 
Refresh the website page 
Click on the first row showing the domain name or visited link (with status 200)
In the right-hand column, you’ll see the response headers. The last header refers to the cache:
<h3>VARNISH CACHE HEADER</h3>
X-VC-Cache: HIT = the resource (page) is present in cache and was served from the Varnish cache system. This means the caching system is working properly. 
X-VC-Cache: MISS = the resource (page) is NOT in cache and was generated by the WordPress application. This means the cache system was instructed by headers or custom rules not to serve the cached content to the visitor.
<h3>NGINX CACHE HEADER</h3>
x-cache-status: HIT or STALE = the resource (page) is present in cache and was served from the NGINX cache system. This means the caching system is working properly. 
x-cache-status: MISS = the resource (page) is NOT in cache and was generated by the WordPress application. This means the cache system was instructed by headers or custom rules not to serve the cached content to the visitor.
<h3>ENABLING THE CACHING SYSTEM FROM THE WEBPANEL</h3>
The NGINX caching system is enabled by default and doesn’t require any specific settings. 
To enable the Varnish caching system, we recommend checking the dedicated guide: https://docs.ergonet.it/gestione-hosting/impostazioni-cache-server/cache-varnish

Ergonet Cache

Ergonet Cache for WordPress is a free plugin developed by Ergonet srl, an Italian hosting company, to drastically improve the performance of a WordPre …

Daan van den Bergh

OMGF can be downloaded for free without any paid subscription from <a href="https://wordpress.org/plugins/host-webfonts-local/" rel="ugc">the official WordPress repository</a>.
<blockquote>
How could using fonts via Google’s service possibly run afoul of GDPR? The fact of the matter is that, when a font is requested by the user’s browser, their IP is logged by Google and used for analytics. 
 — Lifehacker
</blockquote>
Leverage Browser Cache, reduce DNS lookups/requests, reduce Cumulative Layout Shift and make your Google Fonts 100% GDPR compliant with OMGF!
OMGF is written with performance and user-friendliness in mind. It uses the Google Fonts API to automatically cache the fonts your theme and plugins use to minimize DNS requests and speed up your WordPress website.
<h4>How Does It Work?</h4>
After installing and configuring the plugin, OMGF will automatically start looking for Google Fonts whenever a page is requested on your website.
All Google Fonts are listed in the Optimize Local Fonts section of OMGF’s settings screen. There, you can choose to:
<ul>
<li>Preload fonts to reduce Cumulative Layout Shift above the fold,</li>
<li>Unload fonts that’re not used by you, your theme and/or plugins,</li>
<li>Set a Fallback Font Stack (OMGF Pro required), to further reduce Cumulative Layout Shift, or</li>
<li>Replace (OMGF Pro required) font-families with system fonts to speed up loading times!</li>
</ul>
<h4>Other Features include</h4>
<ul>
<li>The integrated Google Fonts checker notifies you if a plugin or your theme has added Google Fonts (e.g. after an update) it can’t process.</li>
<li>Variable Fonts support,</li>
<li>Automatically Remove unused subsets to reduce the size of the CSS stylesheet up to 90%!</li>
<li>Remove Resource Hints (preload, preconnect, dns-prefetch) pointing to <code>fonts.googleapis.com</code> or 
 fonts.gstatic.com,</li>
<li>Ensure text remains visible during webfont load by forcing the font-display attribute to your Google Fonts,</li>
<li>Ensure text remains visible during webfont load by forcing the font-display attribute to all your other fonts! ( 
OMGF Pro required),</li>
</ul>
<h4>Additional Features in OMGF Pro</h4>
<ul>
<li>Run the Google Fonts checker in the frontend (for all users) to organically check for present external Google Fonts throughout your site.</li>
<li>Smart Preload automatically configures which fonts should be preloaded i.e., loaded early to reduce Cumulative Layout Shift, Largest Contentful Paint and <a href="https://daan.dev/blog/how-to/ensure-text-remains-visible-during-webfont-load/" rel="nofollow ugc">Ensure Text Remains Visible During Webfont Load</a>.</li>
<li>Automatically configures itself to make sure all externally hosted Google Fonts on your site are hosted locally. OMGF Pro supports:
<ul>
<li><code>@font-face</code> and <code>@import</code> statements inside inline <code><style></code> blocks,</li>
<li><code>@font-face</code> and <code>@import</code> statements inside local stylesheets loaded by e.g. your theme and/or plugins,</li>
<li><code>@font-face</code> and <code>@import</code> statements inside externally hosted stylesheets loaded by your theme and/or 
plugins,</li>
<li>Web Font Loader (<code>webfont.js</code>),</li>
<li>Async Google Fonts (loaded using JS)</li>
<li>Material Icons.</li>
</ul>
</li>
<li>Multisite and WPML support.</li>
<li>Whitelabel stylesheets, which removes branding and comments from the stylesheets to further reduce the size.</li>
<li>Modify your fonts’ <code>src: url()</code> attribute to fully integrate with your configuration,
<ul>
<li>Use this to serve fonts and the stylesheets from your CDN, or</li>
<li>To serve fonts from an alternative path (e.g. when you’re using Security through Obscurity plugins like WP Hide, 
etc.), or</li>
<li>Anything you like!</li>
</ul>
</li>
<li>Developer Mode, which allows you to easily migrate between Development, Staging/Testing, Acceptance and Production 
environments.</li>
</ul>
<a href="https://daan.dev/wordpress/omgf-pro/" rel="nofollow ugc">Purchase OMGF Pro</a> | <a href="https://daan.dev/docs/omgf-pro/" rel="nofollow ugc">Documentation</a> | <a href="https://daan.dev/docs/omgf-pro/tested-themes-plugins/" rel="nofollow ugc">Tested Plugins & Themes</a>

OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.


Does the job flawlessly. Thanks for making this plugin!


Just works!

Good plugin

OMGF automagically caches the Google Fonts used by your theme/plugins locally. No configuration (or brains) required!

Ergonet Cache vs OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.