PROVIDER Β· Lightweight WordPress optimisation plugin
Perfmatters
Perfmatters, maintained by US developer Brian Jackson, is a paid-only WordPress plugin that disables unneeded plugin scripts per page and tunes loading, fitting plugin-heavy, first-paint sensitive sites whose owners will diagnose item by item.
4pts
Pros
Cons
Product Information
Detailed Notes
Overview
Perfmatters is maintained by US developer Brian Jackson and appeared around 2019, a rare pure-paid WordPress plugin with no free tier. Its philosophy differs from caching plugins by turning off unneeded requests rather than compressing and caching.
Its most common use is disabling plugin scripts per page, since WordPress slowness often comes from loading contact form, store, and slider scripts everywhere. Perfmatters loads them only where used, and that gain is usually more direct than switching hosts.
The limit is judgement. Disabling scripts can break features and must be tested item by item, it provides no page cache so a caching plugin is needed alongside, and being closed source with per-site annual licensing raises portfolio costs. It suits owners willing to diagnose rather than install and forget.
Core Strengths
- Per-page script disabling keeps form, store, and feature scripts off pages that do not need them
- Lazy loading, resource preload hints, and font localisation cut third-party requests and blocking
- Script and query monitors reveal which plugins slow pages down
- Lightweight by design with negligible overhead and no extra front-end requests
Product Ecosystem
Script management
Disable specific plugin scripts by page or post type. Change one item at a time and test, since batch disabling makes it hard to find which change broke a feature.
Loading and resources
Lazy loading, preload hints, and font localisation in one place. Localising fonts removes third-party requests benefiting both privacy and first paint, but confirm the licence permits self-hosting.
Drawbacks
- Disabling scripts can break features and needs item-by-item testing, a higher bar than caching plugins
- No page caching, so a caching plugin is required alongside
- Closed source with per-site annual licensing that adds up for portfolios
- No free tier, so there is no trial before purchase
Use Cases
- WordPress sites with many plugins (β β β β β) - Per-page script disabling delivers the most direct gain
- First-paint sensitive content sites (β β β β ) - Fewer requests and blocking improve CWV
- Sites needing page caching (β β β ) - Pairs with a caching plugin, limited alone
- Owners who avoid configuration (β β ) - Item-by-item testing raises the entry cost
Pricing
| Plan | Price | Scope |
|---|---|---|
| Single-site licence | Annual | Updates and support included |
| Multi-site licence | Annual | Priced by site count |
| Agency | Annual | Bulk licensing and priority support |
Annual pricing scales with site count and there is no free trial. Diagnose with free tools such as Lighthouse and query monitors first, since host response or database bottlenecks are outside what Perfmatters can fix.
FAQ
-
Does it conflict with caching plugins? Usually complementary, with caching avoiding page regeneration and Perfmatters avoiding unneeded assets. Both touch scripts, so avoid optimising the same resource twice.
-
Can disabling scripts hurt SEO? It can if content or structured data disappears. After disabling, verify rendering and rich results, especially reviews, ratings, and product schema.
-
Is it worth buying? Usually for WordPress sites with many plugins, where fewer requests pay off. Sites with few plugins gain little, and budget is better spent on hosting and image optimisation.