Judging from the bandwidth WebOnline said MyADSL 'allegedly' used, I think we should come up with a plan for the site. If we can all come up with feasible, implementable ideas we can have MyADSL local again using far less bandwidth. A couple of ideas from my side so far..:
1) The number of replies per page should rather be 10 instead of 20, that should just about halve the bandwidth already
2) We should craft a decent style sheet which would remove most of the repeated formatting code
If there is any PHP or CGI server-side app which can compress the HTML before the page is sent to the user that would also shave a good 10-20KB. I compressed page 1 of the Telkom 4GB poll and it lopped off whole 20K, quite a lot of bandwidth if the site is receiving around a million hits!
Any ideas from peepz how to get this site streamlined? If we can get this sorted, MyADSL will not only use much less bandwidth, but will also be that much faster.
rpm, what do you fink?
<font color="navy"><font size="1"><b>Where others have progress, we have Telkom.</b>
Hellkom website - www.hellkom.co.za</font id="size1"></font id="navy">
1) The number of replies per page should rather be 10 instead of 20, that should just about halve the bandwidth already
2) We should craft a decent style sheet which would remove most of the repeated formatting code
If there is any PHP or CGI server-side app which can compress the HTML before the page is sent to the user that would also shave a good 10-20KB. I compressed page 1 of the Telkom 4GB poll and it lopped off whole 20K, quite a lot of bandwidth if the site is receiving around a million hits!
Any ideas from peepz how to get this site streamlined? If we can get this sorted, MyADSL will not only use much less bandwidth, but will also be that much faster.
rpm, what do you fink?
<font color="navy"><font size="1"><b>Where others have progress, we have Telkom.</b>
Hellkom website - www.hellkom.co.za</font id="size1"></font id="navy">