SleekView Charts for Flying Pages
SleekView Charts reads the flying_pages_* options, the per-URL prefetch log and the underlying post and link tables. Preload coverage, hover-prefetch ratios and template-level link counts become Number, Pie, Bar and Area cards instead of one switch in Settings.
♾️ Lifetime License available
Preload is invisible until you can count it
Flying Pages does its job in three lines of JavaScript: prefetch internal links on hover, on viewport entry, or on idle, scoped by the rules the site owner sets in flying_pages_* options. From the visitor's side it just feels fast. From the admin side there is essentially nothing to look at: an options page with a few toggles, an exclusions textarea, and no read of how much of the site is actually getting preloaded.
SleekView Charts gives Flying Pages the back panel it never had. A Number card tallies posts and pages eligible for prefetch under the current ruleset. A Pie splits prefetch mode usage across hover, viewport and idle, derived from the rules. A Bar groups internal-link counts per template, surfacing which page types funnel the most prefetch candidates. An Area trends prefetch events per day, pulled from the optional event log the front-end script can ship into a custom table.
The same dataset the table view exposes drives the charts, so a filter for excluded URLs or for a single post type applies to both surfaces. Nothing is recomputed in a separate report tool, and the front-end behaviour stays exactly as Flying Pages intends: passive prefetch, gated by its own rules, just now visible at an aggregate level.
Workflow
Turn Flying Pages options and link graph into a dashboard
Read the prefetch rules
Inventory the internal link graph
Compose the chart cards
Save and share
Sample dashboard
Charts you can build from Flying Pages data
Eligible URLs total
Count
Prefetch candidates by mode
Count
group by prefetch_mode
Internal links per template
Sum(internal_link_count)
group by page_template
Prefetch events per day
Count
group by event_date
Comparison
Default Flying Pages settings vs SleekView Charts
Default Flying Pages settings
- Settings screen shows toggles and a rule textarea with no coverage number
- No view of how many URLs actually qualify for prefetch
- No split of prefetch candidates across hover, viewport and idle modes
- No template-level breakdown of internal link counts
- No time series of prefetch events to confirm a tuning change worked
SleekView Charts
- KPI card for URLs eligible for prefetch under the current ruleset
- Pie split across hover, viewport and idle prefetch modes
- Bar of internal links per template for layout optimisation
- Area trend of prefetch events per day from the event log
- Same dataset behind the table and chart views with shared filters
Features
What SleekView Charts gives you for Flying Pages
Coverage as a number
Render Flying Pages rules as a KPI of eligible URLs plus a pie of prefetch modes. The settings screen tells you what is on. The dashboard tells you what it covers.
Filters span table and chart
Filter to excluded URLs, to a specific post type or to a single template, and both the chart cards and the underlying table stay in sync on the same dataset.
Share a read-only snapshot
Send a stakeholder a URL of the prefetch coverage dashboard or export the filtered set to CSV. Performance reviews get a measurable picture instead of a yes-or-no toggle status.
Audience
Who builds Flying Pages charts dashboards with SleekView
Performance leads
Track eligible URLs and prefetch-mode split as KPIs, then trend prefetch events over time to confirm a tuning change moved the needle rather than just looked plausible.
Template designers
Group internal link counts by template to spot which layouts funnel the most prefetch candidates, then refactor the heavy-link templates first instead of guessing.
Agency support
Give junior staff a read-only dashboard of Flying Pages coverage so they can answer client questions about prefetch behaviour without access to settings or rule editors.
The bigger picture
Why a passive prefetch plugin still needs a coverage panel
Flying Pages is intentionally a thin layer of JavaScript with a tiny settings screen, and that is precisely its appeal. The cost of that minimalism is that there is no admin surface for the questions that matter past install day. How many URLs on the site actually qualify under the current ignore rules.
Which templates funnel the most prefetch candidates. Whether a recent exclusion tightened or loosened the surface. Whether prefetch volume is trending up or down with the content calendar.
None of that is visible from the toggle screen. SleekView Charts reuses the rules, the link graph and the optional event log to build a real coverage dashboard: a KPI of eligible URLs, a pie of prefetch modes, a bar of internal links per template and an area trend of prefetch events per day. Same prefetch behaviour on the visitor side.
Completely different governance posture on the admin side.
Questions
Common questions about SleekView Charts for Flying Pages
The flying_pages_* options, the wp_posts and wp_postmeta tables for the internal link graph, and the optional prefetch event log if the front-end script is configured to ship events into a custom table. No premium add-on is required on the Flying Pages side.
Only for the time-series cards. The KPI, pie and bar work off the static ruleset and link graph and run with zero front-end instrumentation. Sites that want trends over time can wire the prefetch event hook into a small custom table that SleekView reads alongside the rest.
No. SleekView reads cached postmeta, options and a precomputed link index in the admin. Front-end prefetch behaviour is entirely Flying Pages, untouched. Visitors get the same passive prefetch they had before, and the admin gets a dashboard that updates as content and rules change.
Yes. The internal link graph is joined to wp_posts, so all chart cards accept a post type filter. A site that only wants to measure prefetch coverage on product pages can scope the entire dashboard to that type with one filter applied across all four cards.
Yes, if the event log is enabled. Group by event_date with an Area or Line card and a Count aggregation to see prefetch events per day or per week. Without the event log the static cards still capture coverage shifts as posts are added or rules change.
Yes. Any filtered set behind a chart card exports as CSV with the same columns the table view would show. Performance leads use this to brief a developer on the high-link templates or to share a quarterly coverage report with stakeholders.
Yes. Flying Pages sits on the client side and is independent of page caching plugins like WP Rocket, FlyingPress or LiteSpeed Cache. SleekView reads from the same static data either way, so the charts are valid on caching-heavy and caching-free stacks alike.
Yes. Each subsite has its own flying_pages_* options and its own link graph, and SleekView respects that scope. A multisite network sees one dashboard per subsite, mirroring how Flying Pages itself behaves when activated network-wide.
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