=== Tilltrace for WooCommerce ===
Contributors: tilltrace
Tags: woocommerce, performance, page speed, core web vitals, checkout
Requires at least: 5.9
Tested up to: 7.0
Requires PHP: 8.0
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Find what's slowing your WooCommerce checkout, cart, and product pages — real-user performance monitoring with plugin, script, and hook attribution.

== Description ==

Tilltrace measures real WooCommerce performance from your storefront and turns it into clear,
actionable findings: where checkout, cart, and product page time is going, your Core Web Vitals
(LCP, FCP, TTFB, INP, CLS), and which plugins, scripts, and hooks add the most latency.

Features:


* Real-user timing for product, cart, and checkout — total time plus a step-by-step breakdown.
* Per-plugin, per-script, and per-hook attribution so you can see what's actually costing you.
* Script source attribution — each script is traced to its origin (plugin, theme, custom code,
  external/third-party such as tag managers and pixels, or WordPress/WooCommerce core), so heavy
  scripts outside your plugins are surfaced, not just plugin scripts.
* Core Web Vitals from real page visits, including the LCP element.
* Performance insights with concrete, prioritized recommendations.

Tilltrace diagnoses entirely from your live traffic — it never disables plugins, alters requests,
or runs anything on your storefront. Nothing on your store is ever changed to produce a finding.

Tilltrace is a connected service: the plugin collects performance telemetry on your store and
sends it to the Tilltrace API, which returns the analytics, insights, and diagnostics you see in
your dashboard. No telemetry is sent until you explicitly connect your site (see *External
services* below).

== External services ==

This plugin connects to the Tilltrace performance-monitoring service to provide its analytics and
diagnostics. The connection is enabled only after you connect your site (explicit opt-in) and is
required for the plugin's monitoring features to work. The plugin cannot provide analytics,
insights, or diagnostics without communicating with the Tilltrace service.

Service: Tilltrace API — https://api.tilltrace.dev
Purpose: receives anonymized WooCommerce performance telemetry and returns analytics, insights,
and recommendations.

Performance telemetry is retained by Tilltrace according to the Privacy Policy and only for
analytics and diagnostic purposes.

What is sent, and when:

* On connect: your site URL and the API key you provide (to authenticate the site).
* Per page view, after connect (sampled): product/cart/checkout load timing — total and step
  durations, per-plugin timing, script timings (URL, handle, size, cache state, and source
  origin), Core Web Vitals (LCP/FCP/TTFB/INP/CLS), device class, the page path, and an anonymous,
  non-reversible salted session identifier used only to distinguish visits. No customer names,
  emails, IP addresses, or order/cart contents are sent.
* Hourly heartbeat: active-plugin list, plugin versions, and environment signals.

All requests are over HTTPS and authenticated. Sampling rate and per-page tracking are
configurable in the plugin settings.

* Terms of Use: https://app.tilltrace.dev/terms
* Privacy Policy: https://app.tilltrace.dev/privacy

== Installation ==

1. Install and activate the plugin (WooCommerce must be active).
2. Go to Tilltrace → Connect in your WordPress admin menu, paste the API key from your Tilltrace
   dashboard, then click Connect. No data leaves your site until you connect.
3. Performance data appears in your dashboard as real visits come in.

== Frequently Asked Questions ==

= Does it send any data before I connect? =

No. Nothing is sent to the Tilltrace API until you enter an API key and connect your site.

= What customer data is collected? =

None. Telemetry is performance-only and uses an anonymous, non-reversible salted session
identifier used only to distinguish visits — never names, emails, IP addresses, or order/cart
contents.

= Is WooCommerce required? =

Yes. Tilltrace is designed specifically for WooCommerce stores and requires WooCommerce to be
installed and active.

= Does Tilltrace change anything on my store? =

No. Tilltrace only measures. It diagnoses from real visits and never disables plugins, alters
requests, or runs anything on your storefront — so it is safe to run on production.

= Is it safe to run on a live production store? =

Yes. All diagnosis comes from passively observing real traffic. There is nothing to trigger and
nothing that modifies your site, so there is no production risk.

== Screenshots ==

1. Diagnose My Store: finds what's slowing checkout, cart, or product from real traffic — with the evidence, ranked suspects, and a recommended fix. Nothing on your store is ever touched.
2. Checkout tab: step-by-step breakdown, top contributors, and ranked root causes — each with impact, confidence, and a specific fix to try.
3. Product tab: separates server response time from frontend assets, so you know whether to fix hosting or page weight.
4. Tilltrace also tells you when things are fine — Cart graded A here, with the fastest/typical/slowest breakdown as proof.
5. Cross-fleet Insights: one executive summary across every store, with the highest-priority issue and its root cause surfaced first.
6. Fleet view: monitor every connected store's checkout, cart, and product health from one place — built for agencies managing multiple clients.

== Changelog ==

= 1.0.0 =
* Initial public release. Real-user performance monitoring for WooCommerce product, cart, and checkout pages: total and step-by-step timing, per-plugin / per-script / per-hook attribution, and script source attribution (every script traced to its origin — plugin, theme, custom code, external/third-party, or WordPress/WooCommerce core). Core Web Vitals from real visits (LCP, FCP, TTFB, INP, CLS) including the LCP element, plus prioritized recommendations. Diagnoses entirely from live traffic — never disables plugins, alters requests, or runs anything on your storefront, so it's safe on production.
