Skip to main content
Perfmatters logo

Perfmatters

Fine-tune WordPress performance with script unloading, JavaScript delay, Remove Unused CSS, local analytics, bloat controls, and database cleanup.
Visit Plugin
Last Updated: October 16, 2026

Quick take

Perfmatters is a paid WordPress performance plugin for people who want granular control over front-end bloat, scripts, CSS, JavaScript timing, local analytics, database cleanup, and WordPress defaults without replacing a dedicated page-cache layer. Its strongest use case is a site that already has good server or plugin caching but still needs page-specific asset control and practical Core Web Vitals tuning. I would choose it when control matters more than one-click automation.

Perfmatters features at a glance

Perfmatters combines lightweight global toggles with deeper tools such as Script Manager, Delay JavaScript, Remove Unused CSS, local Google Analytics, preloading controls, lazy loading, database optimization, CDN rewriting, and WooCommerce-specific cleanup. It is intentionally designed to work alongside a caching plugin or host-level page cache rather than acting as the only layer in every performance stack.

What can you do with Perfmatters?

You can remove WordPress features the site does not use, unload plugin assets where they are unnecessary, delay or defer JavaScript, generate page-specific used CSS, reduce third-party requests, host analytics locally, improve media loading, tune preloads, and clean database overhead. The practical value is that you can solve performance problems at their source instead of only compressing the final page.

Perfmatters paid options and plans comparison

Perfmatters is paid-only. The current plans use the same core feature set and mainly differ by the number of licensed production sites.

PlanAnnual priceLicensed sitesBest fit
Personal$29.95/year1Single site owners
Business$59.95/year3Freelancers and small portfolios
Unlimited$124.95/yearUnlimitedAgencies and larger site portfolios

When a simpler setup is enough

You may not need Perfmatters if a small site already passes its real-user performance targets with host caching and a lightweight theme, and there is no meaningful plugin bloat to control. Adding optimization plugins without a measured problem can create more exclusions and maintenance than benefit. Start with hosting, theme quality, image size, and unnecessary plugins before adding a fine-grained optimization layer.

When you need Perfmatters

Perfmatters becomes valuable when you can identify assets or WordPress behaviors that should not run everywhere. Examples include a form plugin loading on pages without forms, WooCommerce scripts loading on non-store pages, third-party JavaScript delaying interaction, or large theme stylesheets creating unused CSS. It also fits teams that want explicit control over these decisions rather than delegating them to a fully managed cloud optimizer.

Main settings and WordPress bloat controls

The main Perfmatters interface groups common performance toggles so you can disable unneeded WordPress features without custom snippets scattered across a theme. Treat each toggle as a production change, not a checklist item. Features such as XML-RPC, feeds, emojis, embeds, heartbeat behavior, and WooCommerce assets can have functional dependencies, so disable only what the site does not use.

JavaScript optimization

Perfmatters separates JavaScript controls into a dedicated workflow. Deferring scripts can reduce parser blocking, while delaying scripts until interaction can remove substantial work from the initial render. Aggressive delay settings can also postpone menus, consent tools, forms, analytics, ads, or conversion tracking. Test the full interaction path, especially above the fold, after enabling a broad delay policy.

Reducing unused JavaScript

PageSpeed Insights often flags JavaScript that is downloaded but not needed during initial use. Perfmatters can address this with script timing and, more importantly, Script Manager unloading. The goal is not to make every warning disappear. The goal is to prevent scripts from executing on pages where the feature is absent while keeping dependencies intact on pages that need them.

Remove Unused CSS

The Remove Unused CSS feature processes styles and creates a reduced set of CSS needed by the page. This can lower render-blocking work and improve LCP, but dynamic components deserve careful testing. Menus, popups, sliders, tabs, modal windows, filters, and content loaded after interaction may depend on selectors that are not obvious from the initial page state.

Using browser coverage for CSS decisions

Chrome Coverage can help identify stylesheets with large unused portions, which is useful before deciding whether to rely on automatic used-CSS generation or unload an entire stylesheet with Script Manager. A stylesheet showing high unused percentage is not automatically safe to remove. Test alternate templates, responsive breakpoints, hover states, logged-in views, and conditional components.

Script Manager

Script Manager is one of the strongest reasons to choose Perfmatters. It lets you control plugin CSS and JavaScript by location instead of accepting site-wide loading. A booking plugin might need assets only on booking pages, while a contact-form plugin may need them only where the form exists. Document every unload rule so another administrator understands why an asset is disabled.

Local Google Analytics

Perfmatters can host the Google Analytics script locally, reducing a third-party request and giving you more control over caching. This does not remove privacy or consent obligations, and local hosting does not make analytics exempt from regional rules. Verify that tracking still fires correctly after changes, including ecommerce and consent-driven events where applicable.

Preloading and resource priorities

Preloading can help browsers fetch genuinely critical fonts, images, or other resources sooner, but overusing preload competes with assets that the browser would otherwise prioritize. Preload only resources needed early in the page lifecycle. For LCP images, fonts, and critical requests, validate the network waterfall rather than adding hints based on guesswork.

Database optimization

Database cleanup is useful for revisions, transients, spam, auto-drafts, and other accumulated data, but it is different from front-end speed optimization. Back up before destructive cleanup and avoid running aggressive recurring cleanup against data another plugin expects to retain. On large stores or membership sites, database query performance and object caching may matter more than simply shrinking table size.

Using Perfmatters with page caching

Perfmatters is commonly paired with a page cache from the host, a caching plugin, or a CDN. Keep ownership clear. Let one layer own full-page caching and use Perfmatters for asset and WordPress optimization unless there is a documented reason to overlap features. Duplicate minification, lazy loading, JavaScript delay, or unused-CSS processing can create hard-to-debug regressions.

WooCommerce performance

WooCommerce sites benefit from removing store assets where they are not needed, but cart, checkout, account pages, product variations, fragments, tracking, and payment scripts must remain reliable. Test logged-in and logged-out sessions. A performance rule that works on a blog template may be unsafe on a purchase flow.

Building an asset-control policy

Script Manager works best when the team defines a rule for why an asset may be disabled. Start from the feature location, not from a PageSpeed warning. If a stylesheet belongs to a form plugin, determine every template where the form can appear, including popups, reusable blocks, shortcodes, and conditional widgets, before unloading it elsewhere. Prefer rules that remain understandable six months later. A short internal note beside each major unload decision can prevent a future editor from adding a component to a page where its required assets have already been disabled.

Testing exclusions across templates

Perfmatters changes can be template-specific, so a homepage test is not enough. Maintain a small regression set that includes a blog post, archive, landing page, search page, product, cart, checkout, account page, logged-in view, and any custom post type with special scripts. Test responsive navigation and consent behavior too. When enabling Remove Unused CSS or broad JavaScript delay, compare this regression set before and after the change. The fastest configuration is not useful if a rarely visited but commercially important template breaks.

Change management and rollback

Performance tuning should be reversible. Export or record working settings before a major cleanup, make one category of change at a time, and clear the relevant cache after each change. If an optimization causes a regression, revert the smallest responsible setting rather than disabling the entire plugin. On client sites, keep performance settings under change control just like code deployments. This makes future troubleshooting faster and reduces the temptation to accumulate permanent exclusions that nobody remembers.

Performance ownership across the stack

Assign each optimization job to one layer. Let the host or cache plugin own full-page caching, let Perfmatters own the asset rules you deliberately configure, and avoid enabling duplicate minification, lazy loading, or JavaScript delay in multiple plugins. This ownership map makes troubleshooting much faster because you know which system is responsible for a changed response, script, stylesheet, or media behavior.

What to know before choosing Perfmatters

Perfmatters rewards teams that are willing to understand what their site loads. Its granular controls can produce excellent results, but careless unloading creates missing styles or broken interaction. It also does not remove the need for good page caching, hosting, images, and theme architecture. Think of it as a precision layer, not a magic replacement for the rest of the stack.

Who Perfmatters fits best

I would shortlist Perfmatters for performance-conscious WordPress owners, agencies, WooCommerce teams, and developers who want precise asset control. It is less suitable for someone who wants a completely hands-off managed service and does not want to investigate scripts, exclusions, or template-specific behavior.

Choose Perfmatters if you want granular control over WordPress bloat, scripts, CSS, and JavaScript alongside an existing cache layer. Choose a more automated service if you prefer the optimizer to make most page-level decisions for you.

Perfmatters pricing

Pricing checked October 16, 2026. Perfmatters costs $29.95 per year for Personal on one site, $59.95 per year for Business on three sites, and $124.95 per year for Unlimited sites. All current plans include one year of updates and premium support. Renewals receive the vendor’s current renewal discount, and a 30-day money-back guarantee is offered.

Current version and compatibility

The current Perfmatters release is version 2.6.9, dated October 6, 2026. Recent changes include Remove Unused CSS improvements and compatibility work for modern page builders and large inline scripts. Because Perfmatters can change when assets load, run regression tests after meaningful updates on sites with complex front-end behavior.

PluginSuggest verdict

Perfmatters is a strong choice when you already understand where a WordPress site is wasting requests and want the tools to remove that waste precisely. Its pricing is simple, its site limits are easy to understand, and it pairs well with a separate cache layer. The value comes from disciplined configuration, not enabling every optimization switch.

Perfmatters FAQs

Is Perfmatters free?

No. Perfmatters is a paid-only WordPress performance plugin.

How much does Perfmatters cost?

Pricing checked October 16, 2026: Personal is $29.95/year for one site, Business is $59.95/year for three sites, and Unlimited is $124.95/year.

Does Perfmatters replace a caching plugin?

Not necessarily. Perfmatters is often used alongside host-level caching or a dedicated page-cache plugin, with Perfmatters handling asset and WordPress optimization.

What is the Perfmatters Script Manager?

Script Manager lets you selectively disable plugin CSS and JavaScript on pages or locations where those assets are not needed.

Can Perfmatters remove unused CSS?

Yes. Perfmatters includes Remove Unused CSS and supports exclusions for styles that must remain available for dynamic components.

Can Perfmatters delay JavaScript?

Yes. It provides JavaScript defer and delay controls, including exclusions for scripts that must run earlier.

What version of Perfmatters is current?

Perfmatters 2.6.9 is the current release as checked on October 16, 2026.

Similar Plugins

Premium

Quick take FlyingPress is a paid WordPress performance plugin built for people who want strong page caching and frontend optimization…

Community Reviews

0 community reviews
Log in or create an account to write a review.
No published community reviews yet.