Current time: 02-26-2021, 12:15 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
JavaScript Menu Experiment
07-14-2010, 08:15 PM
Post: #3
RE: JavaScript Menu Experiment
Hey Markus,

I am going to assume you mean assets 33-34 as opposed to 23-24.

Notice on the non-JavaScript menu that the CPU usage is a lot less intense. Perhaps that effects either A) how fast the DNS lookup gets initiated or B) how fast the DNS results are interpreted?

The CPU usage was pretty close to 100% for awhile so I think something in the third-party JavaScript menu code was very inefficient.

If you compare Exhibit A down to asset 32, it takes about 3.4 seconds to load and Exhibit B takes about 2.4 seconds to load to asset 31.

I am not saying that all JavaScript menus are really bad for page speed. However, the Zapatec menu that I am currently using makes pages load a lot slower.

After the menu is transformed into pure CSS, I plan to take all my JavaScript and place it at the bottom of each page instead of the header.

Sincerely,
Travis Walters
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: JavaScript Menu Experiment - LeptienM - 07-14-2010, 06:20 PM
RE: JavaScript Menu Experiment - green-watch.org - 07-14-2010 08:15 PM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)