Thank you for using W3 Total Cache, the only web host agnostic Web Performance Optimization (WPO) framework for WordPress trusted by millions of publishers, web developers, and web hosts worldwide for more than a decade.
Thanks to the wp.org community and the users active in our GitHub repository we’ve fixed the following issues:
Fixed WP-CLI redirect issue in multisite
Fixed PHP empty needle warnings with HTML minify enabled
Fixed HTML Minifier blank output (PREG_JIT_STACKLIMIT_ERROR)
Fixed specifying URIs with a query string in Additional Pages - Performance->Page Cache->Additional Pages parameter was not processing URIs with query string correctly and didn’t purge such pages when Cache URIs with query string option is enabled.
In our public repository on GitHub, you can review our source code, post issues, and even submit Pull requests. You are welcome to join us there, and we really appreciate all users that have contributed, both past and present.
We are always looking for ways to improve W3 Total Cache with new features, UI improvements, and of course, improvements to the user experience. If you like what we have done, please be sure to take some time and rate our plugin on the WordPress Plugin Repository.
Once again, we are sending a big thanks to all of our supporters, including those who are active in the forums helping end-users.
Thank you for using W3 Total Cache, the only web host agnostic Web Performance Optimization (WPO) framework for WordPress trusted by millions of publishers, web developers, and web hosts worldwide for more than a decade.
In this patch release we fixed the reported issue with missing images caused by Lazy Load and CSS minify:
Fixed CSS minify URL rewrite logic that affected some lazy loading and CSS URL addresses using protocols
We would like to thank the users in the WordPress community for reporting the issue and for their patience.
In our public repository on GitHub, you can review our source code, post issues, and even submit pull requests. You are welcome to join us there, and we really appreciate all users that have contributed, both past and present.
We are always looking for ways to improve W3 Total Cache with new features, UI improvements, and of course, improvements to the user experience. If you like what we have done, please be sure to take some time and rate our plugin on the WordPress Plugin Repository.
Once again, we are sending a big thanks to all of our supporters, including those who are active in the forums helping end-users.
Thank you for using W3 Total Cache, the only web host agnostic Web Performance Optimization (WPO) framework for WordPress trusted by millions of publishers, web developers, and web hosts worldwide for more than a decade.
We are proud to announce a new Pro feature in the 0.14.0 release, Lazy Loading for Google Maps. We focused on the compatibility with three major Google maps plugins:
If you are using one of these three plugins you can enable Lazy Loading in Performance>User Experience, select the box next to the plugin you are using, save all settings, and purge the cache. Congratulations, your Google Maps are now lazy-loaded! Please note that this feature is only available after upgrading to Pro!
We have also fixed reported issues and made other improvements:
Added a filter w3tc_minify_css_content for minified contents
Fixed a minify regex issue in non-Unicode websites
Fixed a PHP notice in WPMU: accessing array offset on null
Fixed a minify issue where embedded CSS URL fragments were converted incorrectly
i18n improvement (plugin settings translation)
Changed default to disabled for wp-admin requests in the object cache
In our public repository on GitHub, you can review our source code, post issues, and even submit pull requests. You are welcome to join us there, and we really appreciate all users that have contributed, both past and present.
We are always looking for ways to improve W3 Total Cache with new features, UI improvements, and of course, improvements to the user experience. If you like what we have done, please be sure to take some time and rate our plugin on the WordPress Plugin Repository.
Once again, we are sending a big thanks to all of our supporters, including those who are active in the forums helping end-users.
Thank you for using W3 Total Cache, the only web host agnostic Web Performance Optimization (WPO) framework for WordPress trusted by millions of publishers, web developers, and web hosts worldwide for more than a decade.
With this minor release we fixed the following:
Fixed HTML minification of <img> elements containing embedded SVG strings
Removed an identifying value for GDPR
In our public repository on GitHub, you can review our source code, post issues, and even submit pull requests. You are welcome to join us there, and we really appreciate all users that have contributed, both past and present.
We are always looking for ways to improve W3 Total Cache with new features, UI improvements, and of course, improvements to the user experience. If you like what we have done, please be sure to take some time and rate our plugin on the WordPress Plugin Repository.
Once again, we are sending a big thanks to all of our supporters, including those who are active in the forums helping end-users.
Thank you for using W3 Total Cache, the only web host agnostic Web Performance Optimization (WPO) framework for WordPress trusted by millions of publishers, web developers, and web hosts worldwide for more than a decade.
The newest update for W3 Total Cache is here and we will continue to do our part in helping to speed up the web and your WordPress websites while we continually help to improve the user experience for all your visitors.
With this patch release we’ve fixed reported issues and also made some improvements to the following:
Fixed Syntax problems with curly braces that is deprecated in PHP 7.4
Fixed the ability to create a wp-content/cache folder when it is missing
Fixed broken admin bar when global $posts contain non-array
Fixed WP 5.3 issue where Auto Minify was skipping async js scripts added by WP
Added support for separate configs for multisite domain mapping that supports separate CDNs per site when network-enabled
Added ability to remove emojis to help increase performance
Added protection from invalid regex in “Never Cache following pages” option
In our public repository on GitHub, you can review our source code, post issues, and even submit pull requests if you wish to contribute to the project. You are welcome to join us there, and we really appreciate all users that have contributed in both the past and present. Have an idea for a feature suggestion? Drop by and let us know!
We are always looking for ways to improve W3 Total Cache with new features, UI improvements, and of course, improvements to the user experience. If you like what we have done, please be sure to take some time and rate our plugin on the WordPress Plugin Repository.
Once again, we are sending a big thanks to all of our supporters, including those who are active in the forums helping end-users.
The newest update for W3 Total Cache is here and we will continue to deliver more speed for your WordPress websites while we continually improve the user experience.
With this minor release we fixed an issue reported after the last update:
Fixed PHP warnings in PgCache_ContentGrabber.php
In our public repository on GitHub, you can review our source code, post issues, and even submit pull requests. You are welcome to join us there, and we really appreciate all users that have contributed, both past and present.
We are always looking for ways to improve W3 Total Cache with new features, UI improvements, and of course, improvements to the user experience. If you like what we have done, please be sure to take some time and rate our plugin on the WordPress Plugin Repository.
Once again, we are sending a big thanks to all of our supporters, including those who are active in the forums helping end-users.
The newest update for W3 Total Cache is here and we will continue to deliver more speed for your WordPress websites while we continually improve the user experience.
In this release we’ve added a new Pro feature: Debug – Purge Stack Trace. This feature allows you to see why your cache has been purged and is located in the debug section. We have also added a “Feature Policy” security header, Removed deprecated get_magic_quotes_gpc(), improved the AMP Extension by ignoring the value of amp query string marker in request if passed without value in config, Improved lazy loading by not processing elements with skip-lazy class or data-skip-lazy attribute, and fixed the caching of query-string normalization redirects so that they are no longer cached when the cache key is normalized by accepting query string arguments, which in turn caused a redirect loop.
In our public repository on GitHub, you can review our source code, post issues or bug reports, and even submit pull requests to contribute to the plugin. You are welcome to join us there, and we really appreciate all users that have contributed, both past and present.
We are always looking for ways to improve W3 Total Cache with new features, UI improvements, and of course, improvements to the user experience for you and your visitors. If you like what we have done, please be sure to take some time and rate our plugin on the WordPress Plugin Repository.
Once again, we are sending a big thanks to all of our supporters, including those who are active in the forums helping end-users.
The newest update for W3 Total Cache is here and we will continue to deliver more speed for your WordPress websites while continually improving the user experience.
In this release we’ve added query string based URL structures to cache AMP pages using a query string, filter of minify options (added support for ‘postprocessor’ option usage programmatically), lazyload picture tag support, removed the footer link “Support Us” option, improved wp_die handling, lazyload handling of content in script tags, lazyload handling of feeds, printing tags coming from feeds, handling of modified posts before wp_rewrite initialized and handling of .htaccess files in regard to EOF (End of File).
Nginx rules have also changed a lot to avoid “location” block conflicts. That change may cause problems on some systems using non-default WordPress rules – keep a backup of your original rules to ensure you minimize issues.
We’ve also fixed Varnish purging and HTML minification of data tags equaling 0.
In our public repository on GitHub, you can review our source code, post issues, and even submit pull requests if you are interested in contributing to the project. You are welcome to join us there, and we really appreciate all users that have contributed, both past and present.
We are always looking for ways to improve W3 Total Cache with new features, UI improvements, and of course, improvements to the user experience. If you like what we have done, please be sure to take some time and rate our plugin on the WordPress Plugin Repository.
Once again, we are sending a big thanks to all of our supporters, including those who are active in the community forums helping out end-users.
In previous W3 Total Cache versions, rules for the Nginx server were not correct when the option “Prevent caching of objects after settings change” in Performance > Browser Cache > General was enabled along with “Rewrite URL structure of objects”. Having both of these enabled caused PHP fallback to be used for all minify assets when utilizing the Disk: Enhanced page cache engine.
W3 Total Cache 0.12.0 removes “location” block conflicts for URL postfix rewrites and adds header directives for all other “location” blocks.
In 0.12. version security headers will also work correctly now, which wasn’t the case before as Minify set to disk was not rewriting when Browser Cache with Prevent Object Caching was used in Nginx
That change may, however, due to problems on some systems using non-default WordPress rules so keep a backup of your original rules to ensure you minimize issues.
Particularly WordPress Networks (WPMU) deployed in subfolders instead of in the root directory of the domain, i.e. myhost.com/myfolder/ for WordPress set up and myhost.com/myfolder/my-blog2/ for subdirectory network blogs.
We are constantly improving W3 Total Cache— and listening to your feedback has allowed us to continue offering a top-notch product.
In this latest release, we are proud to introduce some new features and improvements which will help you further increase the speed and performance of your website.
The first new addition that we would like to highlight is Image Lazy Loading, a completely new and highly requested feature to W3 Total Cache that came directly from our users.
Lazy loading images
Lazy loading images mean that images on websites are loaded asynchronously— after the above-the-fold content is fully loaded all other images are only fetched when they appear in the browser’s viewport. Lazy loading defers the loading of resources on the page until they are actually needed, instead of getting them as soon as the page loads. Loading resources ensures that nothing is gathered until the moment the user actually needs them.
If you’ve used Google Page Speed Insights and examined some opportunities for improvement, you may have seen some suggestions to Defer offscreen Images.
With lazy loading, you are reducing the number of images needed to load the page initially. Fewer resource requests mean fewer bytes to download and reduced competition for the limited network bandwidth available to users.
Lazy loading image has a positive impact on performance by reducing the initial page load time, page weight, and system resource usage.
Improved Statistics
We are also excited to announce the new and improved Statistics page that will help our Pro users get the most out of their caching and locate additional areas of optimization. The improved Statistics page allows you to check the Hit rates and overall effectiveness of every configuration enabled in your General settings.
Enabling the Debug mode for each setting In Performance > General Settings > Debug gives you more detailed information by clicking on a link of the desired setting in Statistics Page.
If for example, Object Cache is disabled, it won’t be available in Statistics
In Performance > General Settings > Statistics you can enable Statistics and customize your desired settings:
Please note that this consumes additional resources and is not recommended to be run continuously.
Example of the Statistic Page (Page Cache):
Other Improvements
We’ve also made some more general improvements in this update to enhance the overall user experience:
Fixed inserting a new line before injecting to Apache Config
Fixed HTML minifier removing the quotes around href attribute
Fixed feeds caching test failing
Added License Expiration Admin Notices in Dashboard (Pro)
Implemented correct headers caching for REST API caching under Disk: Enhanced. including a missing test for REST API cache
Main admin menu and admin bar icons were not reflecting the correct color settings if the user selected a different Admin Color Scheme in their profile settings.
Previous icons were .PNG and have been updated to .SVG to make this possible.
I’ve been using this on my own website for a couple of years now to improve website load speed. Teamed up with MaxCDN it has increased my page load speed a lot. We install it on all of our client’s websites now!
Tried numerous caching plugins. W3 is best, especially for busy sites. Most plugins only cache pages, W3 has so many options. Support is very helpful as well. 5 stars.
This plugin made my web pages load faster than other similar plugins I had tried. When I needed help to exclude my sitemaps from caching, support quickly gave me the help I needed. Thanks!!!
I already knew what W3TC could do for the performance (speed) of my website, but until today I had no experience with their support for the free version of the plugin.
The amount of support they provided me and how much they helped me is outstanding. And that’s all for free. Really great plugin, would really recommend this one!
