Pretty good, but that has lost too many points really. Could do with a '2 metre' option, or just a single tickbox to optimise everything for tracklogs.
Just looked at it in various tools and it is perfectly good to me, more than enough info to determine climbing.
My own old rudimentary script gives:-
TOT: points=1073 climb=1262 dist=108697.03m
It's a question of storage, as much as bandwidth - Phil's utility doesn't store the files - AUK's server retains uploaded files for a few months, there are currently 360 tracklogs and over 1,500 'proposed' GPX files in store.
Sure, but you don't need to store the original file either. Receive it (even if it is huge), convert it, remove unnecessary data/attributes, and then downsample it. Compare it to make sure you haven't damaged it beyond recognition and, if ok, throw away the old huge file and keep the much simpler smaller one. [if not ok, throw away both and provide a suitable error message]. There's no need to store anything bigger than you already are. (Although my stuff does but I have something to download the original large files every day and store them on my own machines at home where storage is cheap as online storage is not required for them).
My own stuff runs on a cheap VPS from OVH. 2GB RAM is enough for the OS, httpd server and my scripts to run on the data. 10GB storage is enough for a minimal OS install and the rest (6GB+) is left for data/logs. All that for £3/month. (Bandwidth is a non-issue, you get 100Mbps unlimited traffic.)