I already spoke about this, don't know what are the other opinions about this.
But having '@javascript' all over the place will have a real impact on the performance of the tests.

What I suggest is to create a single test to see if you have access to the page from the homepage (which needs javascript) then for the other tests go directly to the test page.
This way you will have 2 +1 points, 
- first remove '@javascript' from most of the tests giving a boost on performance
- second, going this way if the homepage is not loading well making the menu not popping up only 1 test will fail (the go to page test), otherwise, since all tests depend on homepage all they will fail without that meaning that the feature is broken.