Tuff Qwestions For Smart Webmasters
 

ok tuff qwestion:

1. I ve heard of a way to packet html,

so that say if the html is 100KB, it will be packated up to like 40K,

the surfer downloads the 40K and his browser opens it,

suposedly, the people on old browsers just get the original 100K version, and people on newer browsers get the 40K one and dont notice the difference, and it saves me bandwdith, and the page loads faster for the surfer,

An even tougher question for even smarter webmasters: who can teach me how to spell?

off topic, but Ive already explained in other threads,

I make to much money to worry abotu grammer and spelling,

Yeah - especially on this board :1orglaugh :1orglaugh :1orglaugh

Here's an even tougher question. What in the statement above is a question?

anyways speling aside,

im very serious about speeding up my page loads,

and saving bandwdith,

so does anyone know how do to it????

lol :321GFY

No such thing.

Yes, you can have your HTML compressed and this can save 50% or more.

But unless you have a story site, your content is pictures and movies, which will not compress anyway,

any "html compressor" will do i guess... then check the users browser with some kind of script and redirect them to the specific pages?
uuhm...

well thats what im talking about,

my page is close to 350Kb, 150Kb is txt, in the html file,

im gonna run all my pictures though photoshop again,

but its the html I really nead to cut down on,

my page is called for, 550,000 times a day for 300,000 uniques,

and only like 200,000 or so are downloading the whole page,

my page run sweet for broadband users,

but 56K users have issues with site loading time,

Im not having trouble paying my bills or keeping the server online at 30mbs,

its all just about the surfers load time,

if I speed it up, it will make the site more productive,

and thats what Im after here

Ok, then if 150K is in text you are in luck.

Apache has somthing called mod_gzip. You can have your html pages zipped on the way to the surfer (so you will be using major cpu cycles though).

As far as I know this is pretty easy to do and all browsers going back many years support compressed content, so you might want to look into it.

ok well html compression does not really answer my qwestion,

1. I have a html file I work with,
2. I upload it, and then I have script which write to it,
top list and gallery script

so is there away implement this compresion after the update,

does any one have any ideas on this,

script names, software names???

thank man, that kinda what I was getting at,

does anyone know exactly what the pros and cons of this are???

my main concerns are compatibility with old browsers,
and whether it will fuck up my updates and my use of scripts which write to html

better hosting company - don't cheap out

lol, im talking load times of 150K html page on a 56K modem,

my server ping times are fine and even with the bandwdith I push the images come up everytime,

no downtime in over a year,

lol

Its no a trivial undertaking.

Here is a link:http://www.innerjoin.org/apache-comp...ml#compression

Bottom line: If you want EVERY single surfer to see it, even with 10 year old damaged browsers, you will need an alternate link like "Click here if your browser is a piece of shit".

Why not break your huge page into multiples?

If your load time is crtical, you cannot reduce the pagesize, your users are dialup, and 150K is text (sounds messed up to me), and you can live with 1% or 2% not being able to read it, compression is worth trying.... MAYBE.

mod_gzip

http://i4net.tv/marticle/mod_gzip/
http://sourceforge.net/projects/mod-gzip/

quote
mod_gzip is an external extension module for the WWW's most popular web server Apache, created in autumn, 2000.

Its implementation allows for using the compression method gzip for a significant reduction of the volume of web page content served over the HTTP protocol.

This will help.

:)

We just wrote some compression software for our hosting and dial up customers it compresses all text and images. We run a tunnel between the customer and us to give users of older browsers the advantage of faster page loads as well. Then on our end we use a custom written real-time compression system which dynamically reduces the size of images by about 3 times with minimal loss of quality then we push it to the end user it loads faster and since we cache the image it?s only served once by you saving bandwidth. It gets pretty in depth based on different scenarios but that?s the just of it.

let me know if you want some more info


137771650

Gzip is allright it works great for text but not all that great images and graphics so you dont really save much bandwidth.

TM3 has the compression option build in... Gone from 200K html to like 50-60K. BW dropped ALOT!

Your right there are other ways to get a good compresion. however the fact that this is free, and that there is tons of support on the opensource network means that this will most likely be the best solution.

Also, he said 150K HTML not 150K html and images.

Take galleryfreak.com for example. its a Thumb TGP. The html alone is 76K using mod_gzip you would most likely see results of compresion down to 8-16K, 8 if its cached.

the use of compresion on this would result in substantial savings in bandwidth costs. assuming of course you have more than one user.

a test of 1000 users would be:
standared: 76 * 1000 = 76,000 KB
mod_gzip: 16 * 1000 = 16,000 KB
potential savings of 60,000kb per 1000 users or 58MB. Now times that by hundreds of thousands of users.


Thats a decent savings.