Oops... forgot the link to the GTMetrix report for My and JoAnn's bet.

http://gtmetrix.com/reports/www.your-ad … m/8p60nlZ5

And the report with relative?

Umm.. I would have to perform a major overhaul of my site to provide that Rolly

But... Back to the orig question: Can I change the editor to kick out an absolute URL vs Relative??

hehe you know what? I'm going to wait for SirAGE to get on and I'm sure he can tell you a LOT more about HTTP requests than I can and why you should definitely be concerned about them.
As for the links I do not think you can alter that in the HTML Editor as it's not common practice to include them for every link on a site, but usually only for external links.

Do keep in mind that for every link you setup as absolute it will reload the entire page again rather than reloading only the parts of the page that are relevant and that have not loaded already (in other words every page will load the banners, the headers, the footers etc. etc.) even though it's already been loaded with the first page. This causes slowness, stress to your server as well as a whole lot more bandwidth.

If those things are no concern of yours then you have a deeper pocket than most people that host their sties as usually that much bandwidth will cost a bit more. Just sayin'

Ohhhhhh SirAAAGGGEEEEE! *this should be real good lol*

Stuart,

I addressed this topic in another thread. So, I am going to copy and paste what I wrote there for your benefit and others contributing to this thread.

-------------------
Chances are your host's httpd conf file allows for 20 requests (possibly more) at a time per IP before another server process is spawned. That means if you changed internal references to relative paths...

For example, from this...

to this...

...it would grab the page and most all of its contents in a single connection (instead of 20+ connections) and speed up the page (any page) significantly.
-------------------

The logic is simple. If you use a relative path, the current http path (browser address bar) is assumed to be the jumping off point.

If you use absolute urls (http paths), you are creating additional DNS lookups (outside the scope of your website) to load an internal asset. HTTP is a stateless protocol. That means after a request is made and fulfilled, NOTHING is carried over to subsequent requests. That means you are looking up the same IP address every time for each link to a page, pdf, image, etc. on your website. It's unnecessary. Moreover, it's amateur.

If after reading this explanation you still choose to use absolute paths for your internal links, you're wrong. Believe it.