I'm courting a new host because of unbelievable speed issues with my current one. My home page has been uploaded to a test server for demonstration purposes and I'm not unpleased with the load time or the consistency of the load time thoughout the day. Compared to where I am now, it's heaven.
Even so, because of the length of my content tree and the size of the database the new host to be has been urging me to try something originally posted by Norman Rouxel to aid someone else having slow home page load time.
It goes like this:
Edit Act_Primary.html and replace
<!--@act NETQUOTEVAR:SECTIONTREE_RAW -->
with
NETQUOTEVAR:TOPLEVELSECTIONS_RAW
look for the fragment
document.write(YahooSections(section_tree))
and replace with
document.write(YahooSections(sections))
So I tried it.
(Since I'm such a monkey see, monkey do dolt with regard to code, I tried the
first part two ways. I wasn't sure exactly how Norman meant for it to be done.)
First
<!--@act NETQUOTEVAR:TOPLEVELSECTIONS_RAW -->
and then
NETQUOTEVAR:TOPLEVELSECTIONS_RAW
It didn't seem to make any difference.
The net result is that the content tree has vanished from all pages, but the home page, which is what the experiment was for in the first place.
Part of the design of the home page is for a prospective buyer to see all the brands I've available. It also permits instant access to all the products for a given brand name. Since I'm reasonably happy with the load time on the test server via the intended new host, I'll probably put everything back like it was. It's a matter of curiosity at this point to see how much faster the home page would load without the content tree.
So I'm trying to gain an understanding of why the change worked everywhere, but the home page.
You probably shouldn't go here unless you have a high speed connection and patience...SupplySpecialties.biz
Charles
Even so, because of the length of my content tree and the size of the database the new host to be has been urging me to try something originally posted by Norman Rouxel to aid someone else having slow home page load time.
It goes like this:
Edit Act_Primary.html and replace
<!--@act NETQUOTEVAR:SECTIONTREE_RAW -->
with
NETQUOTEVAR:TOPLEVELSECTIONS_RAW
look for the fragment
document.write(YahooSections(section_tree))
and replace with
document.write(YahooSections(sections))
So I tried it.
(Since I'm such a monkey see, monkey do dolt with regard to code, I tried the
first part two ways. I wasn't sure exactly how Norman meant for it to be done.)
First
<!--@act NETQUOTEVAR:TOPLEVELSECTIONS_RAW -->
and then
NETQUOTEVAR:TOPLEVELSECTIONS_RAW
It didn't seem to make any difference.
The net result is that the content tree has vanished from all pages, but the home page, which is what the experiment was for in the first place.
Part of the design of the home page is for a prospective buyer to see all the brands I've available. It also permits instant access to all the products for a given brand name. Since I'm reasonably happy with the load time on the test server via the intended new host, I'll probably put everything back like it was. It's a matter of curiosity at this point to see how much faster the home page would load without the content tree.
So I'm trying to gain an understanding of why the change worked everywhere, but the home page.
You probably shouldn't go here unless you have a high speed connection and patience...SupplySpecialties.biz
Charles
Comment