SleekView Feedback for Perfmatters
Perfmatters stores per-site and per-script optimization toggles in perfmatters_options and per-post asset rules in post meta. SleekView renders one feedback card per URL, lets devs and SEOs upvote, and tags entries with status badges so optimization triage stays inside WordPress.
♾️ Lifetime License available
Optimization reviews built on the Perfmatters records
Perfmatters keeps its bloat-removal and script-disabling configuration in wp_options under perfmatters_options, with per-post script rules and asset disables stored in wp_postmeta through the Script Manager. The default admin gives you a clean toggle dashboard and the Script Manager UI, but no public-facing way to see which URLs the team most wants to optimize or which the dev team has already triaged as edge cases for the Script Manager.
SleekView reads the Perfmatters records directly and renders one feedback card per URL where a Script Manager rule applies, or per template if you point the view at a CPT. Pick a numeric column like the post view count as the vote weight, attach a pm_review_status meta for the status badge, and pull the post category as the chip. Devs and SEOs can upvote a page card to flag a broken script disable or to nominate a URL for further Perfmatters tweaks, and the increment writes back to the meta key you choose.
Because SleekView is read-only against the Perfmatters records, the toggle dashboard and the Script Manager keep working exactly as before. SleekView only adds a parallel review surface that ranks URLs by votes, shows category chips, and exposes status pills so anyone on the team can spot Script broken, Needs disable, and Reviewed pages at a glance.
Workflow
From perfmatters_options to a feedback wall
Point SleekView at the Perfmatters records
Pick vote, status, and category
Embed the board on a public page
Upvotes write back to meta
Sample board
Sample Perfmatters review board
Comparison
Default Perfmatters versus SleekView Feedback
Default Perfmatters admin
- Admin-only toggle dashboard with no public upvote, status pill, or category chip surface anywhere
- No way for devs or SEOs to surface broken disables without filing a separate support ticket first
- Active toggles, broken disables, and stale rules sit in the same dashboard with no review pill
- Filtering by review state requires custom Perfmatters reports and still keeps data inside admin
- Optimization review counts and signal live in spreadsheets instead of the Perfmatters post meta
SleekView Feedback
-
Reads
perfmatters_optionsplus Script Manager rules and joined post meta - Upvote button writes back to your chosen meta key so the score lives with the post
- Status pills map cleanly to Script broken, Needs disable, Reviewed, and Archived out of the box
- Category chips pull the post taxonomy so each card shows the template at a glance
- Saved views let devs share filtered boards like Script broken or Needs disable without code
Features
What SleekView Feedback gives you for Perfmatters
Native Perfmatters support
SleekView speaks the Perfmatters schema. It maps the perfmatters_options key, Script Manager rules, and joined post meta to vote, status, and category fields automatically, so an optimization feedback board can go live in minutes without writing custom Perfmatters hooks at all.
Real upvotes on real URLs
Each Upvote click increments a meta value on the underlying post. The score is queryable, exportable, and visible alongside the Perfmatters Script Manager columns, which keeps the toggle dashboard as the source of truth instead of forking the data into a separate tool.
Saved performance triage views
Devs get scoped saved views like Script broken, Needs disable, or Stale rule. Each view is a stored filter on the Perfmatters records, so the team can hand off triage without rebuilding the filters every morning before the dev standup begins each day at all.
Audience
Three teams that turn Perfmatters into a feedback board
Dev ops teams
Devs see a ranked board of URLs sorted by view count and tagged with review status. Broken-disable URLs float to the top of a Script broken board so they get fixed before the next traffic spike hits the contact page or the agent dashboard during peak hours.
Editorial teams
Editors upvote URLs where they think a script is misbehaving, see the current Script Manager rule on each card, and stop filing duplicate Slack requests. The signal lives next to the post for the dev team to act on at the next planning session.
Agency performance partners
Agencies running Perfmatters across many client sites scope each board per client. Status pills surface URLs that need rule tweaks, and saved view links can be shared with stakeholders without giving them Perfmatters admin access at all.
The bigger picture
Why Perfmatters still needs a feedback loop
Perfmatters strips bloat with surgical precision and saves entire seconds of TTFB across thousands of WordPress sites. But that precision comes with a long tail of edge cases. A toggle that helps one site breaks a script on a single landing page, the Script Manager rule that fixed it three months ago is still applying after the page was renamed, and the team only finds out when a sales rep mentions the form is broken.
The default admin gives a clean dashboard but no view that ranks pages by impact, no public surface where an editor can flag a misbehaving script disable, no way for a dev to share a Needs disable queue without exporting a spreadsheet. The signal exists, it just lives in the wrong room. SleekView gives the Perfmatters records a public, vote-driven home.
Devs get a saved Triage board sorted by view count and review status pill. Editors get a feedback wall where they can flag a misbehaving page without filing a ticket. Agency teams get per-client scoping so each engagement has its own ranked queue.
Nothing about Perfmatters changes underneath, the toggle dashboard stays the source of truth, and the review loop now lives where the team already works.
Questions
Common questions about SleekView Feedback for Perfmatters
No. SleekView reads the existing perfmatters_options and Script Manager rule records that Perfmatters already writes. The only write is the upvote increment, which lands on a meta key you choose so it sits next to the rest of the post data without touching the Perfmatters options or rule meta at all.
Yes. The Upvote button supports guest votes with a per-IP and per-session lock to keep counts honest. If you would rather restrict votes to logged-in users or to specific roles like Developer or Admin, you can flip that in the view settings without touching any code at all.
You map a pm_review_status meta key when you build the view. SleekView shows a colored pill for each value, and any URL without a status simply renders without a pill rather than blocking the card from showing. Devs can update the status by editing the post or via a custom admin column.
Yes. SleekView reads whichever Perfmatters records exist, so sites with CDN Rewrite, DNS Prefetch, and Local Analytics enabled simply expose more chips and pills on each card. The mapping happens at view setup time without any new Perfmatters configuration.
Yes. Every saved view has its own role and capability scope, so you can publish a public editorial feedback wall on the editor hub and a separate Dev Performance queue that only Developers and Admins can see. Both views share the same Perfmatters records underneath.
When the underlying rule meta is removed, SleekView marks the card as archived on the next refresh rather than deleting it. The upvote meta is preserved on the post so you can restore the score if you re-create the rule later, or archive it cleanly if you decide not to restore.
Yes. Every SleekView is available as a shortcode and a Gutenberg block, so you can drop a Script broken view onto an internal dev portal, embed a Needs disable view on a planning wiki, or stitch several views into a single dev dashboard with separate columns side by side.
SleekView paginates and sorts at the database level rather than loading every rule into memory, so a site with hundreds of Script Manager rules still renders the top of the feedback board in well under a second on a normal shared host. Aggregation queries hit indexed columns by default.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout