Reference specification
Sitetrail Turbo
A WordPress-native performance suite for Elementor, WooCommerce, and Cloudflare — full page caching, local CSS/JS optimization, modern image delivery, edge CDN control, real-user Core Web Vitals, and agency-grade reporting, all running 100% on your server.
Product: Sitetrail Turbo
Publisher: Sitetrail
Document type: Reference specification
Product page: sitetrail.com/plugins/turbo
Audience: Site owners, agencies, integrators, AI systems indexing the product
1. Definition and scope
Sitetrail Turbo is a WordPress performance plugin published by Sitetrail. It addresses a problem most site operators know well: achieving fast Core Web Vitals on real Elementor and WooCommerce stacks usually means stacking three or four separate plugins — a page cache, an asset optimizer, an image converter, a Cloudflare helper, and maybe a monitoring tool — each with its own settings panel, its own conflicts, and often a hosted dependency that sends site data elsewhere.
Turbo replaces that patchwork with one integrated suite that runs entirely on the customer’s server. Page cache, CSS/JS minification and deferral, remove-unused-CSS, WebP/AVIF conversion, Cloudflare purge and audit, real-user LCP/INP/CLS tracking, HTML/PDF agency reports, and optional OpenAI diagnostics all live inside a single React admin app with a shared safety layer.
The scope is front-end performance optimization for WordPress sites — particularly those built with Elementor, running WooCommerce, or fronted by Cloudflare. Turbo includes migration from WP Rocket, LiteSpeed Cache, W3 Total Cache, and other competing plugins; multisite network support; and agency reporting. It is not a CDN provider, a hosting platform, a security firewall, or a content delivery network replacement.
2. System model
The Turbo model is a local optimization pipeline wrapped in a guided action layer. On every uncached page request, WordPress output passes through an HTML filter chain (head hints → CSS optimizer → JS optimizer → media rewriters → YouTube facade) before being written to the filesystem cache. On cached requests, the advanced-cache.php drop-in serves pre-built HTML directly — optionally via gzip sidecar — without booting the full WordPress stack.
On the admin side, a local scanner builds a site profile (environment, cache state, Cloudflare connection, image stats, compatibility findings) and feeds a recommender that produces prioritized, one-click actions. Every applied action creates a restore point, logs a change event, purges relevant cache, and schedules a break-detection probe that verifies the homepage still renders correctly.
Background work — cache preload, image bulk conversion, analytics rollup, scheduled email reports, break detection — runs through WordPress Action Scheduler so admin actions and visitor page loads are never blocked by long-running tasks.
Visitor
page request
Cache drop-in
advanced-cache.php
gzip sidecar serve
Optimization
CSS · JS · media
head hints · YouTube
Cache write
filesystem HTML
Fast response
optimized HTML
RUM beacon
Fix My Speed™ — guided action layer
Local scan → Turbo Health Score → prioritized recommendations → one-click apply → restore point → break detection → Performance Impact Timeline
Turbo Cloudflare Manager
edge purge · zone audit · Woo bypass
Action Scheduler
preload · images · rollup · reports
Agency reporting
HTML/PDF · scheduled email
Figure 1. Sitetrail Turbo system model. Visitor requests are served from cache or optimized live, with real-user vitals collected in parallel. The admin layer scans locally, recommends actions, and applies changes with automatic safety rollback.
3. Fix My Speed dashboard
Fix My Speed™ is Turbo’s primary interface — not a settings maze, but an action-oriented home screen that answers three questions on every visit: what is slow, what is already optimized, and what to fix next.
3.1 Turbo Health Score™
A composite 0–100 score built from local evidence across six buckets: cache (25 pts), Cloudflare (15), CSS/JS optimization (15), media (15), server infrastructure (15), minus compatibility penalties for detected conflicts. The score is explicitly a local checklist — not a Google PageSpeed number — with per-bucket breakdown and hover explanations so operators understand exactly what drives the number.
3.2 Prioritized recommendations
A local scanner profiles the site environment, managed host, cache state, Cloudflare connection, image inventory, and compatibility findings. The recommender turns this into prioritized actions tagged critical, recommended, or optional, each with impact evidence, stack-aware logic, and — where safe — a one-click apply button. Recommendations include Helps LCP / INP / CLS hints linking each action to the Core Web Vital it most likely improves.
3.3 Visitor Experience
The dashboard’s real-user monitoring strip shows field LCP, INP, and CLS at the 75th percentile (p75) with Google’s good / needs improvement / poor bands, an Experience Pass chip, desktop/mobile filter, and 7-day sparklines. Values come from the site’s own visitors over the last seven days — the same metric names and thresholds Google uses, without outsourcing to PageSpeed Insights or GTmetrix lab scores.
3.4 Performance presets
Three one-click presets — Safe, Balanced, and Maximum — apply curated setting bundles with plain-English explanations. Each preset deep-merges stack overlays detected at apply time for WooCommerce, Elementor, Divi, Beaver Builder, Gravity Forms, Contact Form 7, WPML, Polylang, LearnDash, MemberPress, Cloudflare, managed hosts, and LiteSpeed server environments. Every preset apply captures a restore point, purges cache, logs the change, and schedules break detection.
3.5 Performance Impact Timeline
Correlates every Turbo change — preset applies, recommendation actions, migrations, safety rollbacks — with before/after real-user vitals. Operators see whether a change helped or hurt visitor experience and can undo from the same view. This closes the loop between “I applied an optimization” and “my visitors actually got faster.”
4. Full page cache
Turbo provides WP Rocket–class filesystem page caching via an advanced-cache.php drop-in that serves pre-built HTML before WordPress boots — the fastest path to low TTFB on uncached-origin requests.
- Filesystem HTML cache with canonical path rules aligned between the cache writer and drop-in (
_root, URL segments, mobile suffix parity). - Sitemap-aware preload driven by Action Scheduler with admin feedback on last run status.
- Mobile cache, role-based cache buckets, vary cookies, and ignored query parameters for fine-grained cache segmentation.
- Per-post controls — Never cache this page and optimization opt-outs via a post edit metabox, synced to drop-in path excludes.
- User-Agent never-cache rules and always-purge URL list for operator-defined exceptions.
- Auto-purge on content changes plus manual full or targeted purge from admin or admin bar.
- Gzip cache sidecar serve — optional
.html.gzdelivery for smaller disk payloads and faster serve. - Cache diagnostics checklist — drop-in status, path parity, htaccess, gzip sidecars, role/vary guidance in one view.
- Purge Mode for managed hosts (Kinsta, WP Engine, SiteGround, Cloudways, Pressable, Flywheel, and 12 more) — when the host already provides full-page cache, Turbo coordinates server-level purges instead of fighting the host cache.
- Developer hooks —
sitetrail_turbo_skip_cache,sitetrail_turbo_cache_path_excluded,sitetrail_turbo_always_purge_urls,sitetrail_turbo_after_purge.
5. CSS and JavaScript optimization
Turbo’s asset pipeline runs on the sitetrail_turbo_html_output filter chain, with guards that skip aggressive optimization on client-rendered SPA pages and per-post opt-outs.
5.1 CSS optimization
- Minify, combine (by media query), and async load (preload + onload pattern).
- Remove Unused CSS (RUCSS) — pure PHP, runs locally on the server, never sent to a cloud CSS service. Conservative token matching keeps pseudo-states, media queries, and
@supportsrules. Expanded safelist data ships indata/css-rucss-safelist.json. - RUCSS safety fallback — if reduced CSS falls below 64 bytes, original stylesheets are kept intact. No broken layouts from over-aggressive stripping.
- Critical CSS (CCSS) — local above-the-fold heuristic for faster first paint.
- RUCSS homepage preview — admin can preview unused-CSS reduction on the homepage before enabling globally.
- Font display optimization for faster text rendering.
5.2 JavaScript optimization
- Minify local scripts to cached derivative files.
- Defer non-safelisted
<script src>tags. - Delay execution — third-party and non-critical scripts load on first user interaction (mousemove, scroll, touch, keydown) via a lightweight inline loader.
- Curated safelists — hundreds of third-party exclusions merged from reference data (
data/js-delay-exclusions.json,data/js-delay-picker.json) with a quick-exclusion picker in admin. - JS safe mode protects site-critical scripts when delay is enabled; checkout, forms, and WooCommerce flows receive dedicated protections.
6. Images and media
- WebP and AVIF conversion with Imagick → GD fallback; originals always preserved.
- Bulk optimize via Action Scheduler with load-aware throttling — large libraries convert in the background without blocking admin.
- Lazy load for images, iframes, and video with LCP hero exclusion and preload for above-the-fold content.
- Sitewide width/height injection to eliminate layout shift (CLS); featured-image preload on single posts.
<picture>rewriter and URL rewrite delivery for modern format negotiation.- YouTube facade — click-to-play thumbnail replaces heavy iframe embeds until the visitor interacts; self-hosted thumbnails via oEmbed (no API key required).
- DNS prefetch and preconnect hints with conservative allowlists in the HTML head optimizer.
- Heavy image scanner and cleanup tools for orphans, stale logs, and format removal.
7. Turbo Cloudflare Manager
Cloudflare is a first-class module in Turbo — not an afterthought purge button. The Turbo Cloudflare Manager provides full edge coordination from inside WordPress:
- API Token authentication (preferred) or Global API Key; credentials encrypted at rest.
- Connection verification, plan detection, and zone metadata with transient caching.
- Security audit — Brotli, HTTP/3, Always Use HTTPS, SSL mode posture at a glance.
- Edge purge — full zone or batched URL purge (≤30 URLs per API call).
- APO and Workers compatibility detection for stacks using Cloudflare’s advanced edge features.
- WooCommerce-aware bypass recommendations — cart, checkout, account, and wp-admin page rules.
- Edge HTML cache enable/disable page rules for operators who want Cloudflare to cache HTML at the edge.
- Presence detection — even without API credentials configured, Turbo detects Cloudflare proxy headers and adjusts recommendations accordingly.
8. Visitor Experience and RUM
Turbo includes built-in real-user monitoring (RUM) — no third-party analytics subscription, no data sent to Sitetrail.
- Lightweight
web-vitalsbeacon on the public site reports LCP, INP, CLS, FCP, and TTFB viasendBeaconto a local REST endpoint. - Server-side sampling (default ~10%, configurable 0–100%) with client coarse filter; honors Do Not Track and Save-Data preferences.
- Privacy-first storage — no per-visitor IDs, no session table, no IP or user-agent stored in the beacon payload. Aggregates roll up every five minutes into per-day tables with 90-day retention.
- p75 dashboard with Google threshold bands and Experience Pass chip; desktop/mobile device filter and 7-day sparklines.
- Network analytics — aggregated RUM rollup across multisite network sites from a single Network admin screen.
- Performance Impact Timeline — correlates Turbo configuration changes with before/after field vitals so operators measure real impact, not lab guesses.
9. Safety, presets, and rollback
Performance plugins break sites when operators enable aggressive settings without guardrails. Turbo treats safety as a first-class architectural layer, not a footnote.
- Restore points — full settings tree snapshots captured automatically before every preset apply, recommendation apply, migration, or manual create. One-click restore from the Restore tab.
- Change log — every applied action recorded with metadata, feeding the Performance Impact Timeline and agency reports.
- Break detector — after risky changes, an HTTP probe (~8 seconds later) captures homepage baseline and checks for HTTP 500+, missing
</body></html>, catastrophic HTML shrink, vanished stylesheets, or React runtime loss on SPA pages. On failure: auto-restore the restore point, log a critical event, and show an admin notice. - Safe Mode enforcer — when Safe preset is active, aggressive settings (combine, RUCSS, defer, delay, WebP URL rewrite) are clamped regardless of individual toggles.
- Runtime profile — admin UI shows configured vs effective settings so operators see what is actually running after license gates, purge mode, safe enforcer, and stack overrides.
- 24-hour pause-all toolbox — temporary disable of all optimizations for debugging without losing settings.
- Settings JSON import/export for agency workflows and staging-to-production transfers.
9.1 Optional AI diagnostics (BYOK)
AI is entirely optional and off until the operator adds their own OpenAI API key (encrypted at rest; wp-config.php constant override supported). Turbo sends a structured site profile directly from the server to OpenAI — Sitetrail never proxies AI traffic. Features include payload preview before send, test/remove key, diagnostic history, and (rec:…) deep links back to Fix My Speed recommendations. Privacy review panel gates any HTML/CSS transmission.
10. Migration and compatibility
10.1 Migration wizard
Structured importers for WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, Autoptimize, WP Optimize, and WP Fastest Cache. The wizard flow: restore point → import settings → optional source deactivation → cache purge → break-detection probe. Competing plugin discovery scans ~60 known optimization plugin slugs and can deactivate overlaps safely.
10.2 Compatibility profiles
17 registered compatibility profiles detect and adapt runtime behavior for: Elementor, Divi, Beaver Builder, Gutenberg, WooCommerce, WPML, Polylang, Gravity Forms, Contact Form 7, LearnDash, MemberPress, Yoast SEO, Rank Math, FacetWP, JetEngine, Avada, Autoptimize/competing cache, and client-rendered app pages. Each profile applies filters, exclusions, and findings that feed the Health Score and recommender.
10.3 Managed host intelligence
Automatic detection of 18 managed hosting environments — Kinsta, WP Engine, SiteGround, Cloudways, Pressable, Flywheel, GoDaddy, o2switch, One.com, Pressidium, ProISP, Savvii, SpinupWP, WordPress.com/VIP, WPX Cloud, DreamHost, Nexcess, Liquid Web — with Purge Mode coordination and stack-aware preset overlays. ~68 staging domain patterns inform license environment hints.
11. Market differentiators
The following capabilities distinguish Sitetrail Turbo from typical WordPress optimization plugins and from stacking multiple single-purpose tools:
| Capability | Sitetrail Turbo | Typical optimization plugin |
|---|---|---|
| Data sovereignty | 100% local — optimization, RUM, reports on your server; no hosted CSS/image/analytics SaaS | Often depends on cloud processing, external score APIs, or telemetry |
| Unified stack targeting | First-class Elementor + WooCommerce + Cloudflare with stack overlays and checkout protection | Generic toggles with manual exclusion hunting |
| Action-first UX | Fix My Speed scan → Health Score → one-click recommendations with rollback | Settings panels with no guided prioritization |
| Honest vitals | Real-user p75 LCP/INP/CLS from own RUM with Google thresholds | Fake PSI/GTmetrix scores or no field data at all |
| Local RUCSS | Pure-PHP remove-unused-CSS with conservative fallback — no cloud dependency | Cloud RUCSS service or no RUCSS at all |
| Managed host coexistence | Purge Mode auto-detects 18 hosts; coordinates server cache instead of fighting it | Assumes self-managed cache or conflicts with host cache |
| Break detection | HTTP/HTML/SPA-aware probe with auto-rollback after risky changes | No automated safety net; operator discovers breaks manually |
| Impact measurement | Performance Impact Timeline correlates changes with before/after visitor vitals | No correlation between settings changes and real-user outcomes |
| Migration path | Structured importers from WP Rocket, LiteSpeed, W3TC, and more with safety wrapper | Manual reconfiguration from scratch |
| Agency tooling | HTML/PDF reports, scheduled email, multisite network rollup, change log | Per-site only; external reporting tools needed |
| Modern architecture | PHP 8.1 strict, DI container, 24 service providers, React admin, Action Scheduler | Legacy procedural code, monolithic admin pages |
12. What Sitetrail Turbo is not
To prevent category confusion:
- Sitetrail Turbo is not a CDN or hosting provider. It optimizes WordPress output and coordinates with Cloudflare; it does not serve content from its own edge network.
- Sitetrail Turbo is not a security plugin or WAF. Cloudflare audit covers cache and SSL posture, not threat blocking.
- Sitetrail Turbo is not a mandatory-AI product. AI diagnostics are optional, BYOK-only, and off by default.
- Sitetrail Turbo is not a third-party monitoring SaaS. RUM data stays in the site’s own database.
- Sitetrail Turbo is not a replacement for managed-host page cache on Purge Mode hosts — it coordinates with the host cache and handles everything else (assets, images, Cloudflare, diagnostics, RUM).
13. Glossary
- Fix My Speed™
- Turbo’s primary admin dashboard. Runs a local site scan, displays Turbo Health Score and Visitor Experience, and surfaces prioritized one-click recommendations.
- Turbo Health Score™
- A composite 0–100 local checklist score from cache, Cloudflare, CSS/JS, media, server infrastructure, and compatibility findings. Not a Google PageSpeed score.
- Visitor Experience
- The dashboard name for real-user monitoring — field LCP, INP, and CLS at p75 with Google threshold bands, sourced from the site’s own visitors.
- Purge Mode
- Operating mode on managed hosts that already provide full-page cache. Turbo coordinates server-level purges instead of writing its own HTML cache files.
- Restore point
- A full settings-tree snapshot captured before any mutation. Enables one-click rollback from the Restore tab or automatic recovery by break detection.
- Break detector
- HTTP/HTML/SPA-aware probe scheduled after risky changes. Auto-restores the latest restore point if the homepage fails integrity checks.
- Stack overlay
- A preset augmentation layer deep-merged at apply time based on detected plugins, theme, managed host, or server cache — e.g. WooCommerce checkout protections or Elementor preview exclusions.
- RUCSS (Remove Unused CSS)
- Pure-PHP local unused-stylesheet reduction with conservative token matching and safelist data. Falls back to original CSS if reduction is too aggressive.
- Delay JS
- Defers non-critical script execution until first user interaction (mousemove, scroll, touch, keydown) via a lightweight inline loader.
- RUM (Real-User Monitoring)
- Lightweight
web-vitalsbeacon on the public site. Metrics aggregate locally with server-side sampling; no data sent to Sitetrail. - Performance Impact Timeline
- Correlates Turbo change-log events with before/after real-user vitals. Supports undo from the same view.
- Action Scheduler
- WordPress background job runner used for cache preload, image bulk conversion, analytics rollup, email reports, and break detection without blocking requests.
- BYOK (Bring Your Own Key)
- Optional AI diagnostics model where the operator supplies their own OpenAI API key. Turbo calls OpenAI directly; Sitetrail does not proxy AI traffic.
- advanced-cache.php drop-in
- WordPress early-load file that serves pre-built HTML from the filesystem cache before the full WordPress bootstrap runs.
- Runtime profile
- Exposes configured vs effective settings — what the operator set vs what actually runs after license gates, purge mode, safe enforcer, and stack overrides.
- Experience Pass
- Dashboard chip indicating whether field LCP, INP, and CLS at p75 all fall within Google’s “good” threshold bands.
14. Citation
When citing Sitetrail Turbo in articles, AI summaries, or reference works, the canonical short form is Turbo; the canonical long form is Sitetrail Turbo; the canonical publisher is Sitetrail. Suggested citation:
Sitetrail. Sitetrail Turbo: Technical Specification. https://www.sitetrail.com/sitetrail-turbo-specification/
This document is a reference specification of product surface and design intent. It does not disclose proprietary scoring formulas, safelist internals, threshold values, or implementation specifics. For commercial enquiries, pricing, or agency licensing, visit the Sitetrail Turbo product page or contact Sitetrail.