Html Pages Loaded faster in all browser .but Html pages every slow in IE6 and IE7

Discussion in 'HTML & Website Design' started by ayyappansan, Nov 2, 2009.

  1. #1
    Dear Friends,

    I am testing my application in all browser.Finally I notice it . My Html pages loaded faster in all browser but In IE6 And IE7 loaded slow .it take too much of time.I am not able to find the cause for this delay .please give any tips to solve this problem
     
    Last edited: Nov 2, 2009
    ayyappansan, Nov 2, 2009 IP
  2. kk5st

    kk5st Prominent Member

    Messages:
    3,497
    Likes Received:
    376
    Best Answers:
    29
    Trophy Points:
    335
    #2
    How about a link to the page?

    The question you asked is equivalent to asking, "How long is a string?"

    cheers,

    gary
     
    kk5st, Nov 2, 2009 IP
  3. ayyappansan

    ayyappansan Peon

    Messages:
    12
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    ayyappansan, Nov 2, 2009 IP
  4. deathshadow

    deathshadow Acclaimed Member

    Messages:
    9,732
    Likes Received:
    1,999
    Best Answers:
    253
    Trophy Points:
    515
    #4
    Most of your speed issues stem from poorly thought out javascripts - on page that frankly from what I'm seeing shouldn't need ANY scripting.

    The first script that is likely causing issues is that stupid wrapping of IE conditionals to send HTTP or HTTPS in them - that hangs rendering waiting for the document.write's to resolve, and what you are writing (links inside conditionals) is likely to force a re-render BEFORE the css is applied (which then does another re-render)...

    For CSS and scripts that frankly, shouldn't be neccessary in the first place. I still maintain that if you have to send different CSS files to every flavor of IE, you don't know enough CSS to make a layout.

    From there, you have some silly image caching script (that's CSS' job), it looks like one of the scripts is parsing document.getElementByID('*') which can take MINUTES to complete in IE, and all of your scripting has no graceful fallbacks for when .js is unavailable.

    On the whole, the page is no winner on other browsers so far as load times are concerned either - mostly stemming from the poorly encoded images in several dozen separate files. 48 images totalling 179k, a 358k object file (some rubbish flash animation - that too can slow down loading in IE given how the plugin works), 324k of scripting (MEIN GOTT!?!) and 118K of CSS (yut da!?!) pretty well explains the 'problem' - said problem being a website over a megabyte in size over 58 files - handshaking alone for all those files could cause anywhere from 6 seconds to a minute of overhead (without even TALKING bandwidth).

    What's causing image size issues is the use of alpha .png and overuse of transparency when it's not needed. There is NOTHING there which could not be optimized down to 'close enough' palettized or pre-composited so you can use a more robust compression like .jpg

    Bottom line, you are using 1 megabyte and 58 files to present 1k of content text and ten content images (all the other images are presentational) - there is little excuse for the HTML for that page to be more than 6k and for the CSS of just the homepage to be more than 8k - or the CSS for an entire site of that layout style to be much more than an additional 2k per unique page... and I don't see ANYTHING on that page which should 'need' javascript assistance - and if you are using scripting for security and/or saving bandwidth, all you've done is accomplish the exact opposite! (which is quite common). Since you have a customer sign-in, the page should be auto re-directed to https SERVER SIDE BEFORE the user sees any content or a login box.

    The markup itself is also filled with issues, as evidenced by the 58 validation errors meaning you don't have HTML, you have gibberish. HTML can't have an ID, using colons in ID's is generally a bad idea, you've got XHTML in your HTML, you do not 'escape' your inlined javascript properly, there are no scripting off fallbacks for your form handling, you open and close HTML and HEAD more than once (that can only be done once per page!), you don't have alt tags on some images, you try to declare a meta outside the valid document HEAD, the page is knee deep in inlined presentational tags and attributes defeating the point of using CSS in the first place, redundant and unneccessary classes, tables for layout,

    As I often tell people - I'd throw it out and start over with clean semantic markup, separation of presentation from content, optimized non-alpha transparency images, and keep your hand out of the javascript and flash cookie jar until something actually warrants it's use.
     
    deathshadow, Nov 3, 2009 IP
  5. boomer_mitra

    boomer_mitra Well-Known Member

    Messages:
    817
    Likes Received:
    4
    Best Answers:
    0
    Trophy Points:
    110
    #5
    well Microsoft has designed and modulated IE7 a little too much so they forgot about html and concentrated over php and css :D
     
    boomer_mitra, Nov 4, 2009 IP