Current time: 02-26-2021, 12:04 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, 06:20 PM
Post: #2
RE: JavaScript Menu Experiment
(07-14-2010 02:53 AM) Wrote:  Hey Guys,

I think we all know CSS menus are better for page speed, but how bad does a JavaScript menu hurt a webpage? Here are my results:

Exhibit A:
Exhibit B:

Exhibit A had the JavaScript menu enabled. For first view, Exhibit A had a document fully loaded time of 4.414s while the non-JavaScript menu had a 2.808s load time. For repeat view, Exhibit A had a load time of 3.275s while Exhibit B had 2.213s. That is huge!

The start render time on first view was the same. However, on repeat view, Exhibit B was 1.124s compared to Exhibit A's 1.473s.

I am going to setup an outsourcing project on rentacoder to take the JavaScript menu and turn it into a CSS based menu. I will post a link here once I have the project posted. All coders are welcome to bid on the project.

Travis Walters

Hi Travis!

I looked at the Waterfalls

From these two it looks like the JS is not the issue for the longer load times, but the enormous Time-to-first Byte and DNS lookups for the assets 23-34? None of these two should be impacted by the JS asset.

If you compare the Waterfalls reducing assets to 1-21 (without JS) and 1-22 (with JS), you see that the result is roughly the same.

Kind regards,
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

Forum Jump:

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