I suppose, but the simplest way isn't always the way things are actually
done. :o)
Browsers want to do stuff in the background while the user is reading
what is already displayed so that it can appear to be faster at loading
the next page the user might navigate to. If NS runs as you say, like a
proxy (the old proxomitron comes to mind) then FF would never know that
those links existed - but as a plug-in I'm not sure what parses the page
first.
BTW, that page loads in a snap now in IE - even a refresh. It might be
cached by my ISP though.
> Either way, by the time the code actually gets to FF itself,
> there are no script tags. Might that affect the source code subsequent to
> the script introduction,causing some kind of lock-up in the loading?
I don't think so, it's a mystery.
>> Most of the links (mostly graphics) are relative links, except the
>> analytics one.
>
> See above. If NS runs as I have described above, relativity or otherwise
> of the script links is purely academic, isn't it?
Yes, it would never be fetched if all of the script containers and their
contents were removed before the browser got the page.
> Unless, of course, some
> of the script subsequent to one of the tags is dependent in some way on
> the script?
Then we're back to lousy web design, IMO there should be any reliance on
JS being enabled. I didn't see anything like that on that page, and I
didn't download and look at the scripts themselves when I read the HTML
page, just noticed that they were there.