Oxford Metadata Ltd

Menu Optimizer is a powerful performance optimization plugin that generates static HTML files for your WordPress menus, dramatically reducing server load and improving page load times.
Real-World Success: This optimization technique helped achieve the first WooCommerce store with a perfect 100/100 mobile score on Google PageSpeed Insights. <a href="https://wp-rocket.me/blog/100-mobile-score-woocommerce/" rel="nofollow ugc">Read the WP Rocket case study</a>
Why Menu Caching Matters
Menu generation requires significant compute time on WordPress and WooCommerce sites. Every page load requires WordPress to: 
* Query the database for menu items 
* Process menu hierarchy 
* Apply filters and hooks 
* Render HTML output
Menu Optimizer eliminates this overhead by pre-generating menu HTML files that are served instantly.
The DOM Size Problem
Google Lighthouse triggers warnings when a page exceeds 1,500 DOM nodes (HTML elements). For e-commerce sites with extensive product categories:
<ul>
<li>A mega menu with 200-300 categories can generate 3,000-5,000+ DOM elements</li>
<li>Each nested menu item multiplies the element count</li>
<li>This exceeds Google’s limits and hurts Core Web Vitals scores</li>
</ul>
Menu Optimizer’s lazy loading keeps your initial DOM size under 1,500 nodes by loading only top-level items (typically 50-100 elements). Submenus load on-demand, maintaining excellent performance.
Key Features
<ul>
<li>Performance Boost – Reduces menu rendering time with static file caching</li>
<li>Multiple Menu Support – Cache and display multiple menus independently on the same page</li>
<li>Horizontal & Vertical Layouts – Supports both menu orientations for flexible placement</li>
<li>Static File Generation – Pre-generates HTML files for instant delivery</li>
<li>Lazy Loading – Top-level items load instantly; submenus load on first hover</li>
<li>Smart Caching – Uses localStorage for even faster subsequent loads</li>
<li>Max Mega Menu Compatible – Fully supports complex mega menu layouts</li>
<li>Easy Integration – Simple shortcode implementation</li>
<li>Translation Ready – Full i18n support with included POT file</li>
<li>CDN Compatible – Works seamlessly with caching plugins and CDNs</li>
</ul>
Performance Benefits
✓ Keeps DOM size under Google’s 1,500-node limit with lazy loading 
✓ Reduces server CPU usage by offloading menu generation 
✓ Decreases Time To First Byte (TTFB) 
✓ Improves Core Web Vitals scores (LCP, CLS, INP) 
✓ Reduces database queries per page load 
✓ Compatible with WP Rocket, W3 Total Cache, and other caching plugins
Perfect For
<ul>
<li>WooCommerce stores with complex category menus</li>
<li>Sites with large mega menus</li>
<li>High-traffic websites</li>
<li>Sites on shared hosting</li>
<li>Performance-critical applications</li>
<li>Stores aiming for 100/100 PageSpeed scores</li>
</ul>
Proven Results
This menu optimization technique was used in a WooCommerce store that achieved a 100/100 Google PageSpeed mobile score.
Learn more: <a href="https://wp-rocket.me/blog/100-mobile-score-woocommerce/" rel="nofollow ugc">WP Rocket Case Study – 100/100 Mobile Score for WooCommerce</a>
<h3>Credits</h3>
Developed by Oxford Metadata Ltd 
Contact: dimitris.vayenas@oxfordmetadata.co.uk
Special thanks to the WordPress community for their valuable feedback and contributions.
<h3>Support</h3>
For support, please visit the <a href="https://wordpress.org/support/plugin/static-menu-cache" rel="ugc">WordPress.org support forum</a> or contact us at dimitris.vayenas@oxfordmetadata.co.uk.
<h3>Privacy</h3>
This plugin: 
* Does not collect any user data 
* Does not make external API calls 
* Does not use cookies 
* Stores cached menu files locally on your server 
* Uses localStorage only for client-side caching (optional)
<h3>Performance Tips</h3>
<ol>
<li>Combine with a caching plugin – Use WP Rocket or similar for full-page caching</li>
<li>Enable lazy loading – The plugin does this automatically</li>
<li>Use a CDN – Serve static menu files from a CDN for global performance</li>
<li>Regenerate regularly – Update cache whenever you modify your menu structure</li>
<li>Customize CSS via Customizer – Use WordPress’s built-in Customizer for menu styling</li>
</ol>
<h3>Technical Details</h3>
File Structure: 
* Top menu file – Loads instantly with page (minimal HTML) 
* Full menu file – Lazy loads on first interaction (complete with submenus) 
* CSS options – None, Max Mega Menu auto-detect, or custom 
* Storage location – <code>wp-content/uploads/menu-optimizer/</code>
Browser Compatibility: 
* Chrome 90+ 
* Firefox 88+ 
* Safari 14+ 
* Edge 90+
Server Requirements: 
* PHP 7.4 or higher 
* WordPress 5.8 or higher 
* Write permissions to uploads directory

Menu Optimizer

Boost site speed with static menu caching. Lazy-load submenus to keep DOM size under 1,500 nodes for better Core Web Vitals.

Themology

SpeedForge is a performance optimization plugin for WordPress and WooCommerce websites. All optimization processes run locally on your server with no cloud dependencies, no external API keys, and no monthly subscription fees. SpeedForge helps improve Core Web Vitals scores and overall page load times through a comprehensive suite of optimization techniques.
<h4>Page Caching</h4>
SpeedForge generates static HTML files with <code>GZIP</code> compression for faster page delivery. The caching system creates separate cache files for mobile and desktop visitors to serve optimized content for each device type. Cache invalidation happens automatically when you update posts, pages, or products. SpeedForge also includes cache preloading to generate cached versions of your important pages before visitors arrive.
<ul>
<li>Static HTML generation with <code>GZIP</code> compression.</li>
<li>Separate cache for mobile devices.</li>
<li>Automatic cache invalidation when content changes.</li>
<li>Cache preloading for important pages.</li>
<li>Compatible with managed hosting cache systems.</li>
<li>Tag-based cache invalidation for precise purging.</li>
<li>Stale-while-revalidate for zero-downtime cache rebuilds.</li>
<li>Adaptive cache TTL per content type.</li>
<li>Browser cache policy headers (Cache-Control, Vary).</li>
<li>Cache hit/miss statistics dashboard.</li>
<li>Smart warmup with priority queue and pause/resume.</li>
<li>WP-CLI commands for cache management.</li>
<li>HTML minification (conservative and aggressive modes).</li>
</ul>
<h4>CSS Optimization</h4>
SpeedForge generates Critical CSS locally to eliminate render-blocking stylesheets. The Critical CSS extraction identifies above-the-fold styles and inlines them directly in the page head, allowing the rest of your CSS to load asynchronously. SpeedForge also minifies and combines CSS files to reduce HTTP requests and file sizes.
<ul>
<li>Local Critical CSS generation.</li>
<li>CSS minification and combination.</li>
<li>Unused CSS removal per page.</li>
<li>Async loading for non-critical styles.</li>
<li>Self-host Google Fonts locally for GDPR compliance.</li>
<li>Self-host third-party CSS from popular CDNs.</li>
<li>Pre-built critical CSS templates for WooCommerce.</li>
</ul>
<h4>JavaScript Optimization</h4>
SpeedForge defers render-blocking JavaScript to improve page load times and interactivity metrics. Third-party scripts like analytics, chat widgets, and social embeds can be delayed until the user interacts with the page. SpeedForge analyzes scripts to identify which files are safe to defer or delay without breaking functionality.
<ul>
<li>Defer loading for render-blocking scripts.</li>
<li>Delay loading for third-party scripts until user interaction.</li>
<li>JavaScript minification and combination.</li>
<li>Smart script analysis to identify safe-to-delay files.</li>
<li>Self-host third-party JavaScript from popular CDNs.</li>
<li>Inline script grouping to reduce DOM parsing overhead.</li>
</ul>
<h4>Image Optimization</h4>
SpeedForge converts images to WebP and AVIF formats using PHP <code>GD</code> or <code>ImageMagick</code> libraries available on your server. The compression algorithm analyzes image complexity to apply appropriate quality settings without visible degradation. SpeedForge implements native browser lazy loading with Low Quality Image Placeholder support to improve perceived performance.
<ul>
<li>WebP and AVIF conversion using <code>GD</code> or <code>ImageMagick</code>.</li>
<li>Smart compression based on image complexity.</li>
<li>Native lazy loading with <code>LQIP</code> placeholders.</li>
<li>EXIF metadata removal.</li>
<li>Auto-resize large uploads.</li>
<li>LCP image preloading with responsive srcset for product, shop, and category pages.</li>
</ul>
<h4>WooCommerce Optimization</h4>
SpeedForge includes specific optimizations for WooCommerce stores. Cart Fragments, which normally load on every page, are disabled when the cart is empty to reduce unnecessary AJAX requests. Variable product data preloads on hover so attribute changes feel instant. Checkout scripts defer until the payment step, and mini-cart content loads only when visitors hover over the cart icon.
<ul>
<li>Smart Cart Fragments that disable when cart is empty.</li>
<li>Variable product data preloading on hover.</li>
<li>Checkout script deferral until payment step.</li>
<li>Mini-cart lazy loading on icon hover.</li>
<li>Store API response caching with ETag support.</li>
<li>HPOS-aware database maintenance (sessions, stock, order items, Action Scheduler).</li>
</ul>
<h4>CDN Integration</h4>
SpeedForge integrates with major CDN providers for automatic cache purging when content changes. URL rewriting serves static assets through your CDN for global performance. Provider-specific cache tag headers enable surgical CDN invalidation.
<ul>
<li>Cloudflare API integration with URL and zone purging.</li>
<li>Fastly with Surrogate-Key and soft purge support.</li>
<li>Bunny.net pull zone purge API.</li>
<li>Generic Webhook with HMAC-SHA256 signatures.</li>
<li>Automatic CDN purge when local cache is cleared.</li>
<li>Provider-specific cache tag headers (Cache-Tag, Surrogate-Key, CDN-Tag).</li>
</ul>
<h4>Bloat Removal</h4>
WordPress loads several features by default that many sites do not need. SpeedForge provides granular control to disable these unused features and reduce page weight. Each option can be toggled independently so you can keep features your site actually uses while removing the rest.
<ul>
<li>Disable WordPress emoji scripts and styles.</li>
<li>Remove Gutenberg block library CSS for classic themes.</li>
<li>Disable jQuery Migrate legacy compatibility layer.</li>
<li>Remove Dashicons for non-logged-in visitors.</li>
<li>Disable oEmbed discovery and scripts.</li>
<li>Disable XML-RPC for improved security.</li>
<li>Remove RSS feed links from page headers.</li>
<li>Prevent self-pingbacks on internal links.</li>
</ul>
<h4>Heartbeat Control</h4>
The WordPress Heartbeat API sends AJAX requests every 15-60 seconds for features like autosave and login session management. SpeedForge lets you control or disable Heartbeat in different contexts to reduce server load and improve admin performance.
<ul>
<li>Disable Heartbeat on frontend pages.</li>
<li>Control Heartbeat frequency in the post editor.</li>
<li>Adjust or disable Heartbeat in the admin dashboard.</li>
<li>Set custom intervals from 15 to 120 seconds.</li>
</ul>
<h4>Preloading & Prefetching</h4>
SpeedForge implements modern browser preloading techniques to speed up navigation. DNS prefetch resolves domain names before users click links. Preconnect establishes early connections to important third-party origins. The Speculation Rules API prefetches entire pages when users hover over links for near-instant transitions.
<ul>
<li>DNS prefetch for external domains.</li>
<li>Preconnect to critical third-party origins.</li>
<li>Custom domain configuration for prefetch and preconnect.</li>
<li>Speculation Rules API for link prefetching on hover.</li>
<li>Configurable speculation eagerness levels.</li>
<li>Hover prefetch for near-instant navigation.</li>
</ul>
<h4>Cloudflare Integration</h4>
SpeedForge integrates with Cloudflare to automatically purge cached content when you update your site. Connect your Cloudflare account using your Zone ID and API Token to enable automatic cache invalidation. Development mode can be toggled directly from the SpeedForge dashboard when you need to bypass Cloudflare caching temporarily.
<ul>
<li>Automatic Cloudflare cache purging on content updates.</li>
<li>Purge entire cache or specific URLs.</li>
<li>Toggle Development Mode from WordPress admin.</li>
<li>Compatible with Cloudflare APO for WordPress.</li>
</ul>
<h4>Database Cleanup</h4>
SpeedForge removes database bloat that accumulates over time. Post revisions, auto-drafts, trashed content, spam comments, and expired transients consume database space and slow down queries. SpeedForge provides manual cleanup tools and scheduled automatic cleanup to maintain database efficiency.
<ul>
<li>Remove post revisions, auto-drafts, and trashed posts.</li>
<li>Clean spam and trashed comments.</li>
<li>Delete expired transients.</li>
<li>Schedule automatic cleanup routines.</li>
</ul>
<h4>Speed Testing</h4>
SpeedForge integrates with Google PageSpeed Insights API to provide speed testing directly from your dashboard. Core Web Vitals metrics are tracked over time so you can measure the impact of optimization changes. SpeedForge maps PageSpeed audit results to specific features and offers one-click fixes for common issues. A/B testing lets you compare different optimization settings to find the best configuration for your site.
<ul>
<li>Built-in Google PageSpeed Insights integration.</li>
<li>Core Web Vitals tracking with history.</li>
<li>Audit-to-feature mapping with one-click fixes.</li>
<li>A/B testing to compare optimization settings.</li>
</ul>
<h4>Managed Hosting Compatibility</h4>
SpeedForge automatically detects managed hosting environments and adjusts its behavior accordingly. On hosts like WordPress.com, Pressable, WP Engine, Kinsta, SiteGround, Cloudways, and Flywheel that provide their own caching systems, SpeedForge disables its page cache feature to avoid conflicts. CSS, JavaScript, image, and WooCommerce optimizations continue to work alongside the host-provided caching.
<h4>External Services</h4>
SpeedForge connects to the following external services. All connections are initiated only by admin actions or explicit feature configuration. No data is sent without user consent, and no visitor tracking occurs.
Google PageSpeed Insights API
When you run a speed test from the SpeedForge dashboard, your site URL is sent to the Google PageSpeed Insights API to analyze page performance and Core Web Vitals metrics. This connection only occurs when you manually initiate a speed test from the admin dashboard. No data is sent automatically and no visitor data is transmitted.
<ul>
<li>What the service does: Analyzes web page performance and provides Core Web Vitals metrics.</li>
<li>What data is sent: The public URL of the page being tested.</li>
<li>When data is sent: Only when an admin manually clicks “Run Speed Test” in the SpeedForge dashboard.</li>
<li>Service: <a href="https://pagespeed.web.dev/" rel="nofollow ugc">Google PageSpeed Insights</a></li>
<li>Terms of Service: <a href="https://policies.google.com/terms" rel="nofollow ugc">Google Terms of Service</a></li>
<li>Privacy Policy: <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></li>
</ul>
Cloudflare API (Optional)
If you enable Cloudflare integration and provide your API credentials (Zone ID and API Token), SpeedForge connects to the Cloudflare API to purge cached content and toggle development mode. This connection only occurs when you configure Cloudflare settings, when cache purging is triggered by content updates, or when you manually purge Cloudflare cache from the dashboard.
<ul>
<li>What the service does: Manages Cloudflare CDN cache for your domain.</li>
<li>What data is sent: Your Cloudflare API credentials (stored locally), zone ID, and URLs to purge.</li>
<li>When data is sent: When content is updated (automatic cache purge) or when an admin manually triggers a Cloudflare action.</li>
<li>Service: <a href="https://www.cloudflare.com/" rel="nofollow ugc">Cloudflare</a></li>
<li>Terms of Service: <a href="https://www.cloudflare.com/terms/" rel="nofollow ugc">Cloudflare Terms of Service</a></li>
<li>Privacy Policy: <a href="https://www.cloudflare.com/privacypolicy/" rel="nofollow ugc">Cloudflare Privacy Policy</a></li>
</ul>
Self-Hosting Third-Party Assets (Optional)
When the “Self-Host Google Fonts” or “Self-Host Third-Party CSS/JS” features are enabled, SpeedForge downloads font files, CSS, and JavaScript from external CDNs (such as Google Fonts, Font Awesome, jsDelivr, cdnjs, and similar public CDNs) and stores them locally on your server. This eliminates external requests from your visitors’ browsers, improving both privacy and performance. The download occurs once (server-side, not visitor-triggered) and the files are cached locally for subsequent page loads.
<ul>
<li>What the service does: Provides publicly available font, CSS, and JavaScript files.</li>
<li>What data is sent: Standard HTTP GET requests to download public assets. No visitor data is sent.</li>
<li>When data is sent: When an admin enables self-hosting and a previously uncached asset is encountered during a page load.</li>
<li>Services: <a href="https://fonts.google.com/" rel="nofollow ugc">Google Fonts</a>, <a href="https://fontawesome.com/" rel="nofollow ugc">Font Awesome</a>, <a href="https://www.jsdelivr.com/" rel="nofollow ugc">jsDelivr</a>, <a href="https://cdnjs.com/" rel="nofollow ugc">cdnjs</a>, and other public CDNs.</li>
<li>Google Fonts Terms: <a href="https://developers.google.com/fonts/faq" rel="nofollow ugc">Google Fonts FAQ</a></li>
<li>jsDelivr Terms: <a href="https://www.jsdelivr.com/terms" rel="nofollow ugc">jsDelivr Terms</a></li>
</ul>
Gravatar Self-Hosting (Optional)
When the “Self-Host Gravatars” feature is enabled, SpeedForge downloads Gravatar avatar images from <code>gravatar.com</code> and stores them locally on your server. This eliminates external Gravatar requests from your visitors’ browsers, improving both privacy and performance. The download occurs server-side when a page containing Gravatar images is first loaded and the avatars are cached locally for subsequent page loads.
<ul>
<li>What the service does: Gravatar provides user avatar images based on email address hashes.</li>
<li>What data is sent: Standard HTTP GET requests to download public avatar images from <code>gravatar.com</code>. No visitor personal data is sent beyond the Gravatar URL hash that is already present in the page HTML.</li>
<li>When data is sent: When the self-host Gravatars option is enabled and a page with Gravatar images is loaded for the first time (or when the local cache has expired).</li>
<li>Service: <a href="https://gravatar.com/" rel="nofollow ugc">Gravatar</a> (operated by Automattic)</li>
<li>Privacy Policy: <a href="https://automattic.com/privacy/" rel="nofollow ugc">Automattic Privacy Policy</a></li>
<li>Terms of Service: <a href="https://wordpress.com/tos/" rel="nofollow ugc">WordPress.com Terms of Service</a></li>
</ul>
DNS Prefetch and Preconnect (Optional)
When DNS Prefetch or Preconnect features are enabled, SpeedForge adds resource hints to your page HTML headers. These hints tell visitors’ browsers to perform early DNS resolution or connection establishment to common third-party origins (such as Google Analytics, Google Tag Manager, Facebook, and popular CDNs). No data is sent from your server; the browser handles these connections natively. These hints only affect page load performance for visitors.
<ul>
<li>What happens: HTML <code><link rel="dns-prefetch"></code> and <code><link rel="preconnect"></code> tags are added to the page head.</li>
<li>What data is sent: None from your server. The visitor’s browser performs standard DNS/connection operations.</li>
<li>When it happens: On every frontend page load when the feature is enabled.</li>
</ul>
Varnish Cache Purging (Automatic, Localhost Only)
When SpeedForge detects a Varnish reverse proxy on the server, it sends HTTP PURGE requests to <code>127.0.0.1</code> (localhost) to clear cached pages after content updates. These requests never leave the server — they are sent to the local Varnish instance running on the same machine. No external network calls are made and no visitor data is involved.
<ul>
<li>What the service does: Varnish is a local reverse proxy cache running on the same server.</li>
<li>What data is sent: HTTP PURGE requests to <code>127.0.0.1</code> containing the URL path to purge.</li>
<li>When data is sent: Automatically when post/page content is updated or when an admin manually clears the cache.</li>
<li>Note: These are strictly localhost requests that do not leave the server.</li>
</ul>
Nginx Cache Purging (Automatic, Same-Server Only)
When SpeedForge detects an Nginx FastCGI cache or proxy cache setup, it sends HTTP purge requests to the server’s own domain to clear cached pages. These requests are directed at the server itself via its own hostname. No external services are contacted and no visitor data is involved.
<ul>
<li>What the service does: Nginx cache is a local caching layer running on the same server.</li>
<li>What data is sent: HTTP GET requests to the server’s own purge endpoint containing the URL path to purge.</li>
<li>When data is sent: Automatically when post/page content is updated or when an admin manually clears the cache.</li>
<li>Note: These requests are directed at the same server and do not contact external services.</li>
</ul>
<h4>Privacy</h4>
SpeedForge processes all optimization locally on your server. CSS minification, image compression, Critical CSS generation, and all other optimization features run entirely on your hosting environment with no external dependencies.
The only external connections are:
<ul>
<li>Google PageSpeed Insights API when you manually run a speed test.</li>
<li>Cloudflare API if you enable and configure Cloudflare integration.</li>
<li>External CDN servers when self-hosting feature downloads assets to serve locally.</li>
<li>Gravatar servers when self-host Gravatars feature downloads avatar images to serve locally.</li>
</ul>
SpeedForge does not include any tracking, analytics, or telemetry. No visitor data is collected or transmitted by the plugin.

SpeedForge


SpeedForge is a great caching plugin for WordPress. It is very easy to set up, even for beginners. The interface is clean, and the settings are simple to understand. After installing it, my website speed improved noticeably. Lightweight, stable, and very user-friendly. Highly recommended!


Great and User-Friendly Caching Plugin

Speed up WordPress with page caching, critical CSS, image optimization, lazy loading, and more.

Menu Optimizer vs SpeedForge