We hope you find something useful here.
A climb split into stages: how far to the top, where it's steep, where to recover. How Climb view came to WattLog.pro and what the ride data showed.
EF, cardiac drift, heart rate trends and cadence efficiency on the Progress page — how to read them, and why my EF rose 29% in one season.
A map of the Progress page: which cards to start with, what each of the 18 shows, why a card can be empty and where to read more. Based on a real season.
Power by grade and the “When you ride” card in WattLog.pro: 63% of FTP on the flat, 98% uphill — and what that says about pacing.
Power curve, critical power, rider profile, records and W/kg on the Performance tab — on my 2026 season. Why the app called me a sprinter.
I built 18 charts and didn't understand them myself. My 2026 season on the PMC, TSB, ACWR and recovery alerts — how to read the Form tab in WattLog.pro.
Time in zones, energy systems and intensity distribution in WattLog.pro on my season: 1 polarised week out of 24, the rest a pyramid.
An hour of riding took 1.4 MB in the WattLog.pro database. With compressed per-ride streams the same database weighs 35 MB, without losing a single sample.
144 km, 400 TSS and a turnaround below St. Anne's Mountain. What the data said about pacing the climbs, and how Power Guide was born.
A 'eat every 45 minutes' timer can't tell threshold from recovery. How WattLog.pro turns kilojoules, intensity and route profile into carb guidance.
Zwift is great for the ride itself, but weak for tracking your form over time. Signs you need a dedicated analytics app alongside it.