Ed Robinson reminds coders that UX is not an additive issue. In fact it is the opposite. And that reductivism can start with the coding of each and every site that was once coded with large-screen-economics in mind.
…The trick is in understanding how mobile sites are different from the standard site that’s designed for the desktop.
First, understand that most websites are built for the large screen.
Let me make this point again: A visitor’s iPhone is literally downloading giant desktop files and resizing them for their 3.5-inch screen once the files reach the smartphone. Needless to say, smartphones and their browsers don’t have the processing power to make this a quick procedure. This is particularly noticeable with images on your site, which should be re-sampled to reduce their size for mobile devices.
Second, optimize even the seemingly “lightweight” components of your site, like the text-based HTML, XML and stylesheet files. All these can be compressed before being sent to the browser, and it can shave a good chunk off of load times when optimized in aggregate, particularly if the site is heavy with these types of files (media sites and other content-rich properties are prime examples).
Third, consider a more aggressive approach to caching settings. If a site owner sets his caching for far-future expires, it will dramatically lower load times, and the site owner will reduce the data traffic between the server and the user’s mobile device: a win on both sides.
The Big Performance Picture
Ultimately, this issue is all about perception. Web performance has long been perceived to be a network issue, an infrastructure issue or a hardware issue. However, web performance has as much to do with the way someone codes and optimizes a site as any other factor in delivering it to the end-user’s device.
This misperception has also masked the fact that load times are about much more than just “being fast.”
Load times directly impact your customers’ experience of your brand and your service.