Does Size (URL Length) Matter?

[SamMan]

Would there be a noticeable difference in load time between these two?...

http://www.foo.com/barimage.jpg
or
http://www.foo.com/images/barimage.jpg

--
SamMan
Rip it to reply

[Joel Shepherd]

SamMan wrote:

Would there be a noticeable difference in load time between these two?...

http://www.foo.com/barimage.jpg
or
http://www.foo.com/images/barimage.jpg

No. Unless the answer is yes. There's really not enough information
there to answer the question.

Certainly, from an HTML standpoint, it hardly matters to either the
web server or the browser.

-- Joel.

[Philipp Lenssen]

SamMan wrote:

Would there be a noticeable difference in load time between these
two?...

http://www.foo.com/barimage.jpg
or
http://www.foo.com/images/barimage.jpg

No, there wouldn't be (if otherwise everything except the path as shown
above is the same).

[xrongor]

there would be if the images directory didnt exist??

www.this.com could point directly to www.foo.com/images/barimage.jpg and
www.that.com could point straight to www.foo.com/barnimage.jpg. and they
both are probably ACTUALLY sitting on something like
webhosting.somewebhost.com/hoster/this/that/otherthing/~samman/default/ or
something like that.

so if your question is "does another level of subdirectory matter" the
answer is no.

randy

"SamMan" <sa*@psfdevrip-it.com> wrote in message
news:XC***************@twister.rdc-kc.rr.com...

Would there be a noticeable difference in load time between these two?...

http://www.foo.com/barimage.jpg
or
http://www.foo.com/images/barimage.jpg

--
SamMan
Rip it to reply

[SamMan]

Thanks everybody... The reason I asked is a coworker is complaining about
putting images in their own dir, and if so, the "path would be too long". As
in my example, they would be only one level down from the HTML doc. I can
guess their reasoning would be "it will take longer for a page to load"....
and this is coming from a person that creates 600k to 800k+ pages full of
images....

--
SamMan
Rip it to reply

[Eric Bohlman]

"SamMan" <sa*@psfdevrip-it.com> wrote in
news:O%*****************@twister.rdc-kc.rr.com:

Thanks everybody... The reason I asked is a coworker is complaining
about putting images in their own dir, and if so, the "path would be
too long". As in my example, they would be only one level down from
the HTML doc. I can guess their reasoning would be "it will take
longer for a page to load".... and this is coming from a person that
creates 600k to 800k+ pages full of images....

The phrase "superstitious learning" comes to mind. The time taken for a
browser to transmit an HTTP request after establishing a connection is an
absolutely negligible amount of a page's load time (don't confuse this with
request latency, which can be non-trivial), and in any case isn't
proportional to the length of the URL in the request due to the packet-
based nature of TCP/IP.

In the programming community, it's quite well known that even the very best
programmers' gut feelings about what is or isn't "efficient" are usually
wildly off. Therefore, the very best programmers actually *measure* things
when efficiency is a consideration rather than trusting their hunches.
Similar considerations apply here.

IMNSHO, the most important consideration in setting up a URL scheme is that
you create something stable so URLs of existing pages don't have to be
changed in the future, breaking existing links.

[Stan Brown]

In article <XC***************@twister.rdc-kc.rr.com> in
comp.infosystems.www.authoring.html, SamMan <sa*@psfdevrip-it.com>
wrote:

Would there be a noticeable difference in load time between these two?...

http://www.foo.com/barimage.jpg
or
http://www.foo.com/images/barimage.jpg

Unless something _very_ strange is going on in the server, the time
difference would be far less than what any human could observe.
Depending on what else is going on, it might even be zero.

--
Stan Brown, Oak Road Systems, Cortland County, New York, USA
http://OakRoadSystems.com/
HTML 4.01 spec: http://www.w3.org/TR/html401/
validator: http://validator.w3.org/
CSS 2 spec: http://www.w3.org/TR/REC-CSS2/
2.1 changes: http://www.w3.org/TR/CSS21/changes.html
validator: http://jigsaw.w3.org/css-validator/