SpeedForge
Speed up WordPress with page caching, critical CSS, image optimization, lazy loading, and more.
5(1 reviews)
·0 active installs·Updated 1 month agoAs of April 2026, SpeedForge is a WordPress cache plugin with 0 active installations and a 5/5 rating from 1 reviews. It has been downloaded 278 times in total. Requires WordPress 6.1+ and PHP 7.4+. Available on WordPress.org since 2026. Recently updated within the last 3 months. Top alternative: WP-Optimize – Cache, Compress images….
5/51 reviews
0active installs
278total downloads
2 monthssince 2026
Overview
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.
Page Caching
SpeedForge generates static HTML files with GZIP 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.
- Static…
Screenshots
Ratings & Reviews
51 reviews
5 ★
1
4 ★
0
3 ★
0
2 ★
0
1 ★
0
Compatibility
| WordPress | 6.1+ requiredTested up to 6.9.4 |
| PHP | 7.4+ required |
Top Alternatives to SpeedForge
Frequently Asked Questions
Changelog
1.0.1
- Fixed: Mixed content errors on sites behind reverse proxies (Hostinger, Cloudflare, AWS ELB, etc.) where HTTPS is terminated at the proxy level.
- Fixed: CSS and JavaScript minified asset URLs now always use the correct protocol (HTTPS) when the site is configured for it.
- Fixed: Page cache now normalizes URL schemes before storing HTML, preventing cached pages from serving HTTP URLs to HTTPS visitors.
- Fixed: CDN URL rewriting failed silently on reverse proxy hosts because site_url() scheme didn’t match the HTML URLs.
- Fixed: Cache handler stale-while-revalidate now properly detects SSL behind reverse proxies via HTTP_X_FORWARDED_PROTO, HTTP_X_FORWARDED_SSL, and HTTP_CF_VISITOR headers.
…and 7 more changes
Contributors
Plugin data sourced from WordPress.org. Analysis and metrics by PluginSift.