What sort of page weight / size should I be aiming for when optimising for mobile?
Question by Simon Scarfe
I’m looking to optimise the mobile browser experience in a small webapp, using the awesome jQuery mobile to do so.
It goes without saying that a user doesn’t want to DL 200k of data, I’m just trying to draw the line between using external and internal URLs. Is there any existing guideline of what sort of page sizes / loading times I should be shooting for? I’d prefer to stick to internal URLs (keep the mobile interface effectively in one place from a maintenance point of view), but am weary of bogging the user down with lots of information that they have no intention of viewing.
Answer by galambalazs
One thing to note is that e.g. iPhone won’t cache components bigger than 25K.
Also consider minifing and gzipping your code. And @jfar got one thing right. HTTP requests can be a huge performance hit, so you may also want to reduce them as much as possible.
Answer by Starx
I would say try to lower your page as much to 100kb, because if u manage to do so loading different pages as per user request might be negligible.
However, loading the big pile of content at a time and using simple javascript show and hide, to display the content in almost realtime manner might impress the viewer too.
