Groundwork

● weight logged   ● period day

● already reached   ● next target   ● further out

Sizes are a rough guide only — roughly 5–8kg per size on average, and size can lag behind the scale. Your own measurements will always tell you more than this estimate.

–

27 Jul – 24 Aug 2026 · Sibionics sensor, ~8,000 readings. A reference from your last CGM run — not live data.

102 logged meals matched to a CGM reading right before eating and the peak glucose in the 2 hours after, from your Lose It → Google Fit sync overlapping your CGM period (27 Jul – 24 Aug). Average rise across all 102: +0.70 mmol/L (median +0.60).

Carb content only weakly predicted the size of the glucose rise (r ≈ 0.34 across 102 meals) — some low-carb meals still produced a rise, and some higher-carb ones didn't.

Meals containing fried, crumbed, tempura or battered items (nuggets, schnitzel, parmigiana, etc.) averaged a noticeably bigger rise than meals without them — this predicted the rise better than carb count alone did.

Small afternoon snacks (3–6pm) showed the biggest average rise — likely because they're smaller, faster-absorbed portions on their own rather than part of a bigger, protein-heavy meal.

Lowest-carb meals still moved glucose slightly — plain boiled eggs, green tea, and diet soda all produced small rises (+0.4–0.6), just from normal digestion/stress response, not sugar.

Some of your biggest-carb meals barely moved it at all — a 52g-carb meal of coleslaw, avocado and tofu produced only a +0.3 rise, and a 52g-carb meal with cheese and onion only +0.7. Compare that to the 58–60g-carb tempura nugget and dumpling meals, which produced +2.1 rises each — similar carb totals, very different outcomes.

The common thread in the low-rise, high-carb meals: whole vegetables, tofu, cheese — slower-digesting or fibre-heavy carbs. The high-rise meals shared fried coatings or steamed dumpling wrappers (refined, fast-digesting starch). This is a more useful pattern to watch than the carb gram count alone.

Combines the original export with anything you've imported since. Matches your weight data source, confirming syncs are consistent.

28 Jun – 14 Sep 2026 · merged from overlapping sensor sources, split across midnight where a night runs past 12am.

Combines the original export with anything you've imported since — daily average.

Everything you enter is stored only in this browser — there's no server, so it won't appear on another device or browser, and clearing site data or switching browsers will lose it. Download a backup regularly, and definitely right after adding anything you don't want to lose.

Restore from a previously downloaded backup file. This replaces everything currently in the app with what's in the file.

Upload the "Daily activity metrics.csv" file from a Google Takeout export (Takeout → Fit → Daily activity metrics). This page reads it entirely in your browser — nothing is uploaded anywhere — and fills in only the days you're missing for weight, steps and heart rate. It never overwrites a day you've already got.

This can't run automatically — Google doesn't let a plain web page like this sign in and pull live data on its own, so it's a manual export-and-upload each time you want to catch up.

A published page like this one has no way to read an image on its own — there's no AI running inside it. Sending a screenshot here in the chat, the way you've been doing, is the way this actually works: I read it and update the tracker for you directly.

Set what you're working toward at each milestone — tap a reward to edit it. Unlocks automatically as your logged weight reaches each target.