photo sizes

[Middleearther]

I am just learning Frontpage to take over my web site. Am trying to do a
photo album but in the slide show they turn out very large. I am resizing
them but, I am confused about what to change.

All the web photos seem to be about 90000 bytes. Do I simply change the size
or the image resolution or aspect ration or what? Change sie or not? How many
pixels. When I size them down to get the bytes less so it won't load slowly,
the picture is not good. I need a simple info as to what to do with the
scannned images. Web smoothing or compressed? What choices do I make when I
resample? I have Photopaint. I just paint the stuff. This is confusing.

 

[Cowboy \(Gregory A. Beamer\)]

Not sure about PhotoPaint, but the norm is the following:

For JPG: Reduce the quality. this value is a percentage.
For GIF: Reduce the number of colors.

If these are impossible, you can also reduce the physical size.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***********************************************
Think Outside the Box!
***********************************************

 

[Murray]

And remember - the target weight for your initial page load is 45-50K
(total - includes all images, code, externally linked files, etc.).

 

[E. T. Culling]

I just wrote all this for someone else. I hope it will help you as well:
Start here:
http://www.eleanorstravels.com/galleryconsiderations.htm
In your image editing program (I don't know Paint either) you will need to
resize and then optimize each image carefully. 550 wide is a good size for
horizontal photos and 450 tall is good for verticals so that your viewers
won't have to scrool. Don't put too much above the photos on the page such
as banners. On this page:
http://www.eleanorstravels.com/LeGrandSlideShow/index.html The horizontals
are 650 and there is very little above the images. That particular show was
made with Ulead's Photo Explorer.
On this page you have to click on photos you choose (rather than 'next'
etc.):
http://www.eleanorstravels.com/Sheffield/index1.htm
Read thru this even though it is for Paint shop Pro:
http://www.eleanorstravels.com/PSPv9/index.htm
Eleanor

 

[Middleearther]

Sorry; forgot to to check the notify of responses button.

Thanks for the replies.

Cowboy, Thanks. That helps.

Murray, HUH?

E.T. Okay. I'll have a go.

Thank you,
M

 

[Middleearther]

PS

Please bear with me. I am trying to take over the site. I had it built by
somone else and an very leary of goofing it up. I don't know a thing about
all of this but am trying to get up to speed. I do appreciate the help.

M

 

[Murray]

Murray, HUH?

A page's weight determines how quickly it downloads from the server, renders
by the browser, and appears on the screen. The heavier it is, the longer
each of these steps takes. Usability experts seem to agree that you have 10
seconds to engage the visitor with meaningful content before your
'clickthrough' rate begins to climb significantly. A typical 56k dialup
connection can transfer about 4K of page content a second. 10 seconds means
that your page must be 40K or less. Practice indicates you can relax that a
bit to 45K or so.

A page's weight is calculated by adding together the weight of the markup on
the page, the weight of all images used on the page, and the weight of all
externally linked files (javascript, Flash, CSS, Java <shudder>, etc.).

Photos tend to be heavy critters. If this page is the FIRST page of the
site, i.e., the home page, you will want to pay particular attention to that
45K target. If this page is an inner page of the site, you can consider
that you have already gotten an intellectual committment of the visitor to
stick with a lengthier download, and relax that number quite a bit,
especially considering that all of the common graphic elements have already
been fetched from the server and placed in the local browser cache - thus,
they load instantly. In addition, the 10 second number is the time required
to present engaging content, so it's possible (on heavier pages) to build
the page so that some content appears quickly and 'distracts' the visitor
while waiting for other content to arrive. See what I mean?

Or is that Too Much Information?