Release v2.6.8
Perfmatters v2.6.8
Latest versionWhat's new in v2.6.8
Perfmatters v2.6.8 was released on . We developed the perfmatters plugin with simplicity in mind. See the full changelog below and compare with the complete version history.
Release details
Released
1.2 MB
File available
Changelog
Added
- new Inline Excluded Stylesheets advanced option to automatically inline stylesheets excluded from Remove Unused CSS.
- new Safe Mode option to disable all Perfmatters performance optimizations sitewide without impacting security-related options or code snippets.
- new Load in Block Editor option for frontend CSS code snippets so those styles can also appear in the WordPress block editor canvas.
- new perfmatters_inline_scripts filter which allows you to inline specific local JavaScript files.
- missing license notices for bundled third-party libraries.
Improved
- stylesheet inlining via the new perfmatters_inline_stylesheets filter (perfmatters_rucss_inline_stylesheets still supported), which can now run independently of Remove Unused CSS while still deferring to RUCSS for non-excluded stylesheets.
- Remove Unused CSS to detect local stylesheets from the URL path, which should resolve most third-party CDN rewrites without needing the CDN URL setting or local stylesheet filter.
Other
- Made some adjustments to code snippets UI visibility script.
- Moved Instant Page, Preconnect, and DNS Prefetch into the main Perfmatters queue so they respect the same request-level disable checks as other front-end optimizations.
Removed
- redundant admin and ?perfmattersoff checks from FastClick output, which is already gated by the main Perfmatters queue.
Fixed
- a PHP warning in Minify class when parse_url() returned false for a malformed script or stylesheet URL.
- a PHP fatal error that could stop buffer optimizations from running when one-per-line options were stored as a string instead of an array.
- an issue where Remove Unused CSS could delay, async, or remove external stylesheets that were never included in used CSS.
- get_file_path incorrectly stripping characters from asset paths on subdirectory installs in certain cases.
- a compatibility issue with Infinite Uploads that prevented code snippets from loading correctly.
- an issue where Perfmatters meta options were not available when creating a new post or page until after saving.
- an issue where code snippet filenames with non-ASCII characters (such as Korean) were incorrectly encoded on disk.
Compatibility
- Requires WordPress
- 5.5
- Tested up to
- 7.1
- Requires PHP
- 8.1
Verified safe
Perfmatters v2.6.8 scanned clean with no security threats detected.
View full scan report