Remove unnecessary comments. However, keep in mind the following caveat: Removing
comments can reduce file size, but it can make it harder to manage your code in the future.
Use shorter filenames. For example, it is much more efficient to reference tb2.png than
TopBannerAlternate2_980.png.
Minimize the total number of external style sheets and JavaScript library files you include with
your page. Because browsers typically make just two requests at a given time, every additional
file that a browser has to wait on for the request to complete will create latency.
Write well - formed and standard XHTML code. While not a bandwidth issue, well - formed
XHTML requires less passes and parsing by Mobile Safari before it renders the page. As a result,
the time from initial request to final display can be improved through this coding practice.
Consider using gzip compression when you serve your application. (See the following section
for more on compression options.)
Consider using a JavaScript compressor on your JavaScript libraries. You could then work with
a normal, un - optimized JavaScript library for development (mylibrary.js) and then output a
compressed version for runtime purposes (mylibrary - c.js). (See the following section for more
on compression options.
Pages:
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242