I’m no Coda support, but I know a thing or two about oversize docs since I deal with them in my coda-expert-for-hire practice way too more often than I’d like to. I outlined a lot in the post linked above. There you can see how to figure out the doc size. For more detailed breakdown (i.e. by table) I composed myself a script to inspect that:
Quick actionable steps to reduce doc size:
Cut down on conditional formatting; ideally remove it wherever you can and replace with emoji or some other colorful labeling. See: This doc is too big to sync
Cut down on controls: replace sliders etc with numbers, replace formula controls with Text or any appropriate type (e.g. if you have a calculated yes/no checkbox, just replace it with Text type — Coda will still treat it as yes/no but doc size will shrink). See: PSA: The hidden cost of Checkbox column for true/false values
Hey, @Ben_Swanson, if you would like to know the (uncompressed) size of your Doc, you have to access the DevTools on Chrome.
For that, while opening your Doc, you have to press Command+Option+i or Ctrl+Shift+i
There’s a tab called Network. Go there and press Command+r or Ctrl+r
On the bottom left of the DevTool, you will see the amount of resources that was loaded for that Doc.
One strategy I have been able to implement is using CrossDoc; I crossdoc my zapier-linked table into a new doc, Zapbook. I copy my original zap and reconnect it from original doc to Zapbook and then map the zap to this sync table. Set sync to hourly.
I have this working on docs that are not able to connect to zapier.