On Jan 27, 2011, at 11:39 AM, tonzodehoo wrote:
Hello Walter.
I’ve checked the images and they all measure the 950px width of the
graphic box the actions been applied to. Some are marginally taller.
They are all 72dpi as well.
They are still way too large in file-size. For example,
calderglen-029.png is 1.41MB all by itself. If you’re going to show
this many images of this pixel dimensions, please save them as JPEG
with low quality, rather than as 24-bit PNG images of fairly high
quality. You need to get these images down to around 70 - 80 KB each.
The one you mention I have edited. All images are now around 1Mb in
size.
When you say a memory leak I thought that this was a purely human
condition!
Let me know if you think this is something which needs further
investigation.
The script appears to be loading each image at least twice. The first
time when the preloader script fires, and the second time when the
image is actually shown. When I watch the site load in Safari’s Web
Inspector, I can see the total file size for the page grow grow grow
as the animation progresses.
I didn’t think the dpi would be an issue but I did suspect that the
physical size would affect how they appeared in the box.
Right, physical (i.e. pixel) size is the only thing that matters on
the Web. All images are always shown as if they were 72ppi, regardless
what the ppi header in the file directs.
Any suggestions?
One or more of the following will help:
-
Compress the living daylights out of these images, and save them in
JPEG format, which is always going to be 8 bits per pixel smaller
(before compression) than PNG, because it doesn’t contain an alpha
channel.
-
Make the images smaller in pixel dimensions.
-
Use fewer images.
Also, be sure to look into a different slideshow script, because this
one is doubling your page size by downloading all of the images twice.
This appears to be your home page for the site. I would recommend
putting these slideshow images on a different page if that’s the case.
Your home page has one and only one purpose in life – to get people
introduced to your content and off of the home page as quickly and
efficiently as possible. You come to the home page, not because it’s
the source of information, but in order to find what you’re actually
looking for. If you had a little graphic on the home page that said “A
day at TASK in pictures”, your visitors could choose to visit it,
would expect it to be a large page (the pictures part would be a dead
giveaway) and would be expecting to wait. Even after you re-compress
these images, they will still be too many and too large for a
comfortable load time over an average connection. Most people will
give up and go elsewhere while they’re waiting 11.9 minutes (over a
full T1!!!) to have your page finish loading.
Walter
actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options