Forum Moderators: not2easy
Is it my images? I don't know - I tend to save my images as Jpg or gif files... Does anyone have any suggestions on how to speed up website loading times dramaticaly? Or at least enough to make a difference.
As a rule of thumb I try to keep all my pages under 15kb (lower if possible). Unless there are some worthwhile illustrations or photo's that are integral to the content.
CSS will reduce code bloat and an external style sheet only need be downloaded once so saves bandwidth.
Other tricks include; server side includes, optional low graphics version, tableless design, repeat imaging and post design code bloat reduction (especially if you design with wysiwyg).
<added> Of course all of this is dependant on the speed of your users connection - 56k Dial Up will be slow when compared with Broadband 512k for example. Other factors that could slow it down could be badly functioning databases, host problems, network provider problems, users PC etc
Ideally you should test on the lowest common denominator - we have a test box on 56k Dial up using IE5</added>
Thank you for your help. =)
This makes a small but noticable speed increase. I've had website reviewers comment on how fast the site loaded.
jdkuehne
Two factors affect perceived speed: size of download, and latency.
The size, e.g. for images, is an obvious issue, and you should always go for the lowest size image that still looks good.
Latency becomes a significant factor if your page contains lots of little images. With poor server/browser settings, each image could require a new HTTP transaction to fetch.
In my experience, the biggest slowdown factor comes from tracker code. The worst case requires:
1. a DNS lookup to load a JavaScript applet.
2. GET the applet
3. execute the applet, often resulting in an additional GET, possibly with another DNS lookup
A server side include [google.com] (SSI) is a method of serving consistent info to your users. For example; you may have navigation and a footer that remains the same on every page - you can use a SSI to serve this information to your users via a server request. this request references just one file that you can keep easy tabs on - so if you want to change you site nav - do it once and the whole site updates - moy useful non? (and easier on the ol' cache too ;) )