✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for WP Meteor

SleekView Kanban reads WP Meteor delay rules from the WordPress options store, groups script handles into lanes like delayed, immediate, excluded, and broken, and lets your team drag handles between lanes to flip script delay behavior from wp-admin.

♾️ Lifetime License available

SleekView Kanban board for WP Meteor

Why WP Meteor delay rules fit a kanban

WP Meteor delays the execution of JavaScript on a WordPress page until the first user interaction, which is the modern technique that turns a slow PageSpeed Insights score into a green one without rewriting any code. Settings live in wp_options under the wp_meteor_options key with the delay timeout, the include rules, the exclude rules, and a per-handle override state that swings between delayed, immediate, excluded, and broken.

The default WP Meteor admin shows global delay settings and a flat list of handles, which works for a quick on or off but breaks down once a site has dozens of script handles and a performance lead needs to audit which handle is delayed, which is excluded, and which broke when the delay shipped. SleekView Kanban reads the same options and groups handles by the delay state, which is the natural pipeline lane for a script delay audit. Each card surfaces the handle name, the source script URL, the size, and the exclude rule.

Dragging a card from delayed to excluded writes the new state back to the WP Meteor exclude list for the handle, so the next request loads the script immediately without delay. Bulk drags can mark a curated set of broken handles excluded in one transaction after a deploy ships, which is exactly how a perf lead wants to keep delays running without breaking critical site features.

Workflow

From Meteor delay list to handle board

1

Point at WP Meteor

Install SleekView next to WP Meteor. Pick the wp_meteor_options row as the source. SleekView reads every handle, every include rule, every exclude rule, and the configured delay timeout from the plugin admin.
2

Pick delay state as the lane

Set the group-by field to the delay state column. SleekView reads every value WP Meteor uses, including delayed, immediate, excluded, and broken, and renders each as a lane with a live count and a color.
3

Choose card fields

Pick which handle fields appear on each card. Most performance leads pick handle name, source URL, file size in KB, and exclude rule match. Full handle dependencies open in a side panel.
4

Enable delay drops

Flip the drag-and-drop switch and SleekView writes the new delay state back to the WP Meteor exclude or include list on drop. Capabilities decide who flips delay rules on production handles in the kanban.

Sample board

Sample WP Meteor delay state board

A live SleekView Kanban grouping WP Meteor handles by delay state, with cards showing handle name, source script URL, file size in kilobytes, and the exclude rule match.
Delayed
84
recaptcha handle delayed until first input
src grecaptcha, size 28KB
analytics handle delayed until first scroll
src ga, size 48KB now
chatbot handle delayed until first user input
src chat, size 64KB JS
Immediate
14
jquery-core handle loaded immediately as is
src core, size 28KB JS
wc-cart-fragments handle immediate on load
src wc, size 4KB now
wp-emoji handle loaded immediately as core
src core, size 12KB JS
Excluded
22
login-form handle excluded by admin rule list
rule path login, skipped
admin-bar handle excluded by admin rule list
rule path admin, skipped
checkout handle excluded by admin rule list
rule path checkout, skip
Broken
3
woocommerce-checkout handle delay broke pay
broken after delay shipped
contact-form-7 handle delay broke submit btn
broken after delay shipped
third-party-popup handle delay broke widget
broken after delay shipped

Comparison

Default Meteor admin vs SleekView

Default Meteor admin

  • Default admin shows global delay settings and a flat list of handles with no state
  • No instant view of how many handles are delayed versus excluded across the whole site
  • Marking a curated set of handles excluded means editing the exclude list textbox line
  • No audit trail of who flipped which handle delay rule during a Core Web Vitals audit
  • Mobile Meteor admin view shows the same dense settings textbox that desktop renders

SleekView Kanban

  • Groups WP Meteor handles by the delay state field with live counts per lane shown
  • Drag from delayed to excluded to add the handle to the WP Meteor exclude rule list
  • Card fronts show handle name, source script URL, file size, and exclude rule match
  • Broken lane lists every handle that visibly broke after WP Meteor shipped a delay
  • Capability gates restrict delay rule flips on production handles to senior perf leads

Features

What SleekView Kanban gives you for WP Meteor

Audit delay state at a glance

WP Meteor delays scripts until first user interaction, but the default admin lists handles with no state grouping. The kanban groups handles by delay state across the site, so a perf lead sees delayed versus broken at a glance.

Spot broken handles fast

The broken lane stands out when a deploy ships and a delayed handle breaks a site feature like checkout or chat. Drag to excluded and WP Meteor stops delaying that handle on the next request to the affected URL.

Filter by source or rule

A filter bar narrows lanes by handle pattern, source URL pattern, file size, or exclude rule match. Saved filters are per-user, so a perf lead chasing third-party scripts keeps a focused board while another watches core handles.

Audience

Three teams using the WP Meteor kanban

Performance engineers

Performance engineers run a Core Web Vitals audit, watch the delayed lane to confirm WP Meteor delays the slowest scripts, and exclude any handle that breaks a site feature from the kanban.

Front-end developers

Front-end developers filter the board to the pages they own, watch the broken lane after every deploy, and exclude any delayed handle that breaks site behavior on production.

Incident responders

On-call responders open the broken lane during an incident, see every delay-broken handle ranked together, and exclude them in one drag so the site is fixed within minutes.

The bigger picture

Why a kanban beats a list for delay rules

Script delay is a precision problem. WP Meteor delays the execution of JavaScript on a WordPress page until the first user interaction, which is the single most effective performance trick for Core Web Vitals on a content-heavy WordPress site. The downside is that delaying a critical handle like a checkout script or a chat widget breaks a site feature, and the default WP Meteor admin presents handles as a flat list with global toggles that make it hard to know which handle is currently delayed and which one quietly broke after a deploy.

A kanban board fixes that shape. Lanes give performance leads an instant count of delayed, immediate, excluded, and broken handles, drag-and-drop turns an exclude rule update into a single gesture that adds the handle to the WP Meteor exclude list, and filters let each lead scope the board to the handle patterns they own. The same delay options power a different mental model that matches how perf teams really think about script delay rules.

Questions

Common questions about SleekView Kanban for WP Meteor

Both versions of WP Meteor store delay options in the same wp_options key, and SleekView reads that key directly. The kanban renders the same way regardless of which version you run, and Pro adds the broken handle detector that fills the broken lane automatically after each deploy.

 

Yes. The drag handler writes the handle to the WP Meteor exclude list in the wp_meteor_options row. On the next request, WP Meteor reads the exclude list and skips the delay for that handle, which means the script loads immediately without waiting for first user interaction.

 

Yes. WP Meteor rules are simple per-handle state flags, so dragging the card from excluded back to delayed removes the handle from the exclude list and restores the default delay behavior for that handle on the next request to any URL that matches the include rule pattern.

 

Yes. SleekView views are configuration only, so you can build one board filtered to third-party handles and another to core handles from the same WP Meteor option set. Each lead picks a default board, and admins pin shared boards into the sidebar for the perf team.

 

SleekView reads the handle set on every page load, so a new handle from a freshly installed plugin shows up automatically as a card in the delayed or immediate lane depending on the WP Meteor include rule. You can drag it into excluded if it breaks a site feature.

 

Each broken card opens a side panel showing the handle name, the source script URL, the file size, the detected break symptom like a JavaScript error or a missing event listener, and the affected page URL. Perf leads can exclude the handle without leaving the kanban.

 

Yes. SleekView respects WordPress capabilities, so you can require a senior performance lead capability before a card lands in the excluded lane for production-tagged sites. Juniors can flip staging exclude rules freely, but only seniors flip production exclude rules.

 

SleekView reads and writes the existing wp_meteor_options row without adding shadow tables for delay state. View configuration sits in its own small options row, so uninstalling SleekView leaves every WP Meteor delay rule and exclude list exactly where the plugin wrote it.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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