TR Forums

Hi everyone. Unfortunately, I am not the most knowledgeable person when it comes to html encoding. As much as I've tried, I can never really grasp the intricacies and form of it. However, being well versed in computers, in general, a friend of mine has asked me about a problem she is having with her husband's web page. The web page she designed will show up perfectly in Firefox and Opera, but fails to load correctly in IE. I've looked over the page sources, but I don't understand enough of it to begin troubleshooting. So, I was wondering if anybody here might be able to lend me a hand.

Her website is http://www.warnerarchitecture.com

Thank you. I would appreciate any help that I can get.

This has nothing to do with encoding. It is more of a Javascript not working in IE issue. When you compose a site primarily in Javascript (that's why it is so hard to understand, I have little clue myself), that's what happens.

I'm in Linux right now, so I can't see the issue, but looking at the source code reveals that you should go to http://www.dynamicdrive.com/ and see if there's an update. It looks like all the JavaScript may have been taken wholesale from there.

Additionally, that one page took a while to load. You might want to see how much you can speed it up. Like, using CSS to create the borders instead of an image.

And if it is a layout issue you're having in IE, then try tweaking the CSS to see if that fixes your problem. The JavaScript may not be your problem.

titan wrote:

Additionally, that one page took a while to load.

It's because all the images for the slide show are loaded at the beginning instead of being loaded asynchronously.

lordtottuu wrote:

titan wrote:

Additionally, that one page took a while to load.

It's because all the images for the slide show are loaded at the beginning instead of being loaded asynchronously.

I was speaking specifically of the border that surrounds the whole thing. That should use CSS instead of an image. The sample images loaded dynamically as they were called. At least, that was my experience.

titan wrote:

lordtottuu wrote:

titan wrote:

Additionally, that one page took a while to load.

It's because all the images for the slide show are loaded at the beginning instead of being loaded asynchronously.

I was speaking specifically of the border that surrounds the whole thing. That should use CSS instead of an image. The sample images loaded dynamically as they were called. At least, that was my experience.

Hmm, so I discovered that image is actually one big honkin' thing. I just deleted some portions of the image that unnecessarily duplicate the background, and I shaved off 100KiB. Given the opportunity, I could probably make it so that only 40KiB is used for the layout. I know that has nothing to do with the problem the OP wrote about, though.

titan wrote:

lordtottuu wrote:

titan wrote:

Additionally, that one page took a while to load.

It's because all the images for the slide show are loaded at the beginning instead of being loaded asynchronously.

I was speaking specifically of the border that surrounds the whole thing. That should use CSS instead of an image. The sample images loaded dynamically as they were called. At least, that was my experience.

Weird. It took me 3 minutes to load on my connection and then all the images loaded fluidly. Lemme go back and check.

The speed problems would be helped considerably if the image sizes were optimized. PNG for the photos is unnecessary, and the background layout could easily be reduced to an 8-bit PNG with no loss of quality.

crazybus wrote:

The speed problems would be helped considerably if the image sizes were optimized. PNG for the photos is unnecessary, and the background layout could easily be reduced to an 8-bit PNG with no loss of quality.

That's what I said. Though not as technically, and a bit more GIMP work to get the job done.

Each PNG file that's being shown in the slideshow is in excess of 400kB per image. Using a high (well, higher quality by JPEG's standards) quality JPEG can cut down on bandwidth by a lot.

430KB
http://www.warnerarchitecture.com/Images/4o5.png

57KB
http://bayimg.com/kaONaaabL

Good catch there, Nitro. Now I wonder when the OP is going to say something here....

Sorry for the lack of response. Like I said, I'm not familiar with webpage encoding or building and it is my friend's website, so all I can do is thank you guys for the help, relay the information, wait and hope.

Thank you all for the quick help and tips.

I'll let you know how it goes...hopefully soon.

krazyredboy wrote:

Sorry for the lack of response. Like I said, I'm not familiar with webpage encoding or building and it is my friend's website, so all I can do is thank you guys for the help, relay the information, wait and hope.

Thank you all for the quick help and tips.

I'll let you know how it goes...hopefully soon.

Well, that Web site is easy enough to get one's feet wet. If paid, I could probably make the thing behave better than it is now in an afternoon. You could probably get it done in a day or two...with the right resources. But do be sure to tell us what ends up happening. And I still didn't check to see what it looks like in IE. I have a system I'm rebuilding right now, so I can't really just pop over yet.

Yeah, I would have to say that the main problem is the fact that every picture on there is 400kB+. Just loading the main page with the slideshow is 2+MiB per view.

I think a big problem is that the website is using flash when there is no reason to. Everything on the site could be done more efficiently in HTML, CSS, and a bit of javascript. By having those pictures embedded in the flash app (which is not written to use dynamic asynchronous loading), the loading problem is made even worse. Tell your friend that if they can find and fix the problem, great. However, it's my opinion that if they have to put a significant amount of money into it it may just be worth starting over from scratch.