Just to get a quick indication of size, I squashed the binary, which results in 18MB of size.
[NOTE: Such is
not an optimal working solution, as QtWeb for portability reason by default places all dynamic user profile files into same dir as which the binary is run from, and of course that needs to be writable. It seems otherwise /tmp is used for dynamic files.]
Arora of which QtWeb seems to be a fork is 25MB from repo.
So, from this perspective, it suddenly looks no longer that bad for a binary which must be including at least webkit and QT.
After some more testing, I found following:
Running QtWeb upx'ed as shipped results in 40MB of initial (about:blank) res mem usage.
Running after un-upx'ing results in 11MB.
(Stripping and/or squashing do not seem to influence initial res mem usage).