## What the Performance page shows Performance is your long-view analytics workspace. It combines completed rides, readiness data, and modeled training load to show how your fitness and form have changed over time. Key facts about the page - Time window: Performance focuses on roughly the last ~90 days of completed, non-duplicate sessions. This gives short‑to‑medium term context for adaptations and trends. - Session set: Completed activities are included; planned workouts that were later matched to completed rides are deduplicated so you primarily see the completed activity with planned context. - Commute filter: You can optionally exclude commute rides when enabled. The app references your profile preference for "exclude commute activities" (this behavior is the default-on in some code paths). - Readiness + load: The page combines readiness time series and training‑load modeling to help you decide whether to push, maintain, or recover. - Weekly eFTP: A weekly eFTP trend (weekly_eftp) gives a rolling view of how your effective FTP changes over multi‑week blocks (typically shown for the most recent ~8 weeks). Use the Performance page when you want to go beyond a single session and answer questions like: Am I getting fitter? Is fatigue accumulating? Has my eFTP moved lately? ## Key charts and how to read them ### Training load (performance management) What it shows - CTL (Chronic Training Load): an estimate of your fitness (longer-term training dose). - ATL (Acute Training Load): recent fatigue (shorter-term training dose). - TSB (Training Stress Balance): form — the difference between CTL and ATL (often used to infer freshness). How to read it - CTL rising steadily over weeks indicates accumulating fitness. - Spikes in ATL with dips in TSB indicate heavy fatigue — expect reduced quality until TSB recovers. - A planned taper shows falling ATL, stable CTL, and rising TSB before a target event. Tips - Short bursts of high ATL are normal after big efforts; watch recovery (TSB) before expecting maximal performances. - Compare CTL ramp rates to the recommendations in adaptive training articles; avoid very steep, sustained rises. ### Readiness series What it shows - Readiness scores by date and short history; these combine signals like recent training load and available health metrics to judge whether your body is primed for intensity. How to read it - Persistent low readiness combined with high ATL is a warning sign — prioritize recovery. - If readiness is high but TSB is neutral, you have a window to hit a high‑quality session. See the dedicated Readiness page for more detail on day‑to‑day signals: /readiness ### Weekly eFTP trend (weekly_eftp) What it shows - A weeklyized view of effective FTP (eFTP) across recent weeks (typically ~8 weeks are visible in the trend lines). How to read it - Look for gradual upward movement rather than one‑off spikes: sustained small gains are meaningful. - Sudden drops in weekly eFTP usually reflect reduced training load, illness, or poor data capture — dig into recent sessions to find a cause. For a deeper conceptual grounding on FTP and durability, see: /knowledge-base/ftp-is-a-snapshot-durability-is-the-real-story and /knowledge-base/understanding-ftp-the-foundation-of-power-based-training ### Session-level summaries and distributions What it shows - Volume and intensity breakdowns for the time window: TSS totals, intensity distribution by zone, normalized power summaries, and the count of sessions contributing to the window. How to read it - Volume (hours / TSS) contextualized with intensity tells whether your gains are coming from endurance or interval work. - A heavier-than-usual intensity load without increased volume is a sign to expect higher fatigue. ## Filters and controls Use the page filters to refine the view: - Time range: while the page centers on ~90 days, you can focus narrower windows inside that span to isolate phases (base, build, taper). - Commute filter: toggle excluding commutes. If you rely on Strava or other integrations, ensure your commute tagging is accurate or enable exclude commute in your profile. - Duplicate handling: planned workouts that match completed rides are shown once with planned context so charts use completed data for analytics. If you need to correct a missing activity or connect a device for better coverage, open Device Integrations: /settings/integrations ## Definitions: short and practical - eFTP (effective FTP): a modelled estimate of your sustainable power that accounts for recent session data. Weekly eFTP tracks meaningful shifts over weeks. - TSS (Training Stress Score): a session’s stress estimate combining duration and intensity. TSS sums drive load metrics (CTL/ATL). - CTL (Chronic Training Load): long‑term training dose; higher → more fitness (with more base fatigue). - ATL (Acute Training Load): recent training dose; higher → more short‑term fatigue. - TSB (Training Stress Balance): CTL − ATL (interpret as form/freshness; higher TSB → fresher). - Normalized Power (NP): power metric that better represents the physiological cost of variable efforts. For deeper reading on zones and how power maps to training, see: /knowledge-base/cycling-power-zones-optimal-training ## Practical workflows - Validate a trend: if weekly eFTP falls, open the recent rides in /training to check for missed FTP tests, poor data, or a sustained low‑intensity block. - When fatigue is high: compare readiness against ATL and plan lighter sessions; the AI Coach can help adapt immediate sessions in real time: /coach - When you want better data: connect Strava, Garmin, Wahoo, or WHOOP on /settings/integrations to improve activity and readiness coverage. Note: Oura Ring shows on Integrations with “full integration coming soon.” Zwift’s planned workout upload is likewise indicated as coming soon. ## Signals to watch (and what to do) - Rising CTL + persistently low TSB: you’re building fitness but piling fatigue — consider a recovery week. - Falling weekly eFTP across several weeks: check total volume, sleep/readiness, and recent illness; don’t panic over a single-week dip. - Large discrepancies between ride power and perceived effort: check device calibration and ensure indoor/outdoor data differences are understood (see knowledge base on indoor/outdoor differences). ## Related pages and articles - Review recent sessions on the Training calendar: /training - Day‑to‑day readiness and immediate guidance: /readiness - Connect devices to improve sync and upload behavior: /settings/integrations - Background reading: /knowledge-base/ftp-is-a-snapshot-durability-is-the-real-story, /knowledge-base/cycling-power-zones-optimal-training, /knowledge-base/understanding-ftp-the-foundation-of-power-based-training ## Troubleshooting & notes - Offline: Performance charts require network to update with new activities. Previously viewed pages may work from cache; see /offline for details. - Beta label: the app is labeled Beta in the header. If you see unexpected behavior, please report it through Help & Support in Settings: open Settings → Help & Support (/settings/support). If you want a quick next step: open Performance, pick a two‑week window where eFTP moved, then jump to /training to inspect the rides that drove that change.