On Apr 23, 12:13 pm, hedgomatic <hedgoma...@gmail.com> wrote:
> While virtually every site in existence trumpets using the jQuery DOM-
> ready shortcut as an absolute must, I've come across situations which
> I feel frustrate the user, particularly when using jQuery to create a
> navigational element.
>
That sounds like a potential accessibility issue.
> I often work on sites which are going to have a lot of external
> content (ads, feeds, analytics), and if even one of them is sluggish
> to load, none of my interactive elements are responsive for that time.
You say you've got ads, feeds, and analytics. Are the ads in iframes?
How are the analytics included? Is it something like Omniture or
ForeseeResults? Such script tags should be moved to just before </
body>.
>
> There seem to be three options:
>
> 1] liveQuery (disadvantage: overhead)
> 2] popping a loading message over the whole page (disadvantage:
> ridiculous)
> 3] nesting an image inside the portion of the DOM we need, and using
> an onLoad event (disadvantage: poor semantics).
>
> Anyone else come across any novel ways around this seemingly under-
> discussed issue?
There are probably more and better options. Possibly by using a
combination of a few things, the performance and user experience (and
possibly SEO) could be improved.
Garrett
