|
26 May 2008 09:33 pm
|
Web performance has been a topic I have been working on for quite some time now. While building Nexaweb’s Ajax library we ran into and solved many challenges that developers will face while developing their own Ajax applications. Most of my effort has been around JavaScript performance and Ajax’s impact on a websites performance.
Ajax’s Impact on site performance
- Increased Number of Requests
- Increased Download Size
- Increased JavaScript Code
Upcoming Webinar
On Thursday at 2:00pm myself and Ryan Breen from Gomez and Ajax Performance.com will be giving a free 2 hour webinar covering all things performance. Usually, I do this webinar by myself, so I am excited to get another person on board to give their perspective on Website performance. Ryan will be talking about:
- Survey tools available for performance analysis
- Establish and follow a site optimization workflow
- Explore real world examples of how to improve the end user experience
▪kk
Go to Webex.com and sign up, its free, you can ask questions and we will be handing out information on how you can optimize the performance of your Website / Web application.
New Release of jsLex
I am never one to just talk about something, if I haven’t put in effort to solve the issue in a repeatable way then I probably wouldn’t talk about it at all. jsLex is a tool I created over a year ago that makes Website Optimization easier for developers build simple.
I have been getting a lot of good feedback on jsLex, which I have incorporating into the plugins since the release a month ago. jsLex 1.1.1 includes code to automatically build the compressed CSS and JavaScript files. The builder listens for changes to resources and when a dependency changes rebuilds the appropriate CSS or JavaScript files. Click here to read more about the feature and how it works.
Just check the box and jsLex will install the first and only Web Optimization builder for Eclipse that I know about.
Anyone having ideas on how to make it better, send me an email, comment on the Blog or create a topic in jsLex’s Yahoo Group.
I hope everyone joins the Webinar on Thursday and downloads the latest jsLex plugins.
Bob (Buffone)
Oh Awesome! Thank you!
whoops, didn’t add any context to my comment. It was regarding the newly added “recreate” feature to jsLex.
[...] blog has more details on how to sign up. It’s free, of [...]
Note that the registration page says the event is only one hour. I assume it’s actually 2 hours?
the webinar is two hours. I will get that taken care of
I know I am posting this on the wrong blog entry. But was just evaluating your JavaScript evaluation page at http://rockstarapps.com/samples/performance/. You do a lot of count variation depending on the browser – like IE, FF, Safari etc. With the counts varying per browser how is this test browser agnostic? Does this not provide a wrong picture to the performance tester.
Thanks
AJAX Developer
Ajax Developers,
I did add in some browser checking in certain places. This was due to that browser performing really POORLY in that test and needed to eliminate the dreaded “Script running to slow”. An Example of this was the weirdness around the pushing and poping array elements.
It’s true that it does make the test not agnostic, but the numbers should be used as a guide to how the tasks perform on each browser rather than precise analytic data.
Bob
Thanks for your reply!
Since the RockStarApps performance tests are quite popular, I think it becomes a requisite to well inform the users (who do not look for the details within the test) about such differences.
Some of the workarounds you could use include:
- Scale down the counts for those tests for all browsers
- Flag such results where tests are not agnostic
Just some suggestions
Otherwise, keep up the great work. These tests are pretty comprehensive. Do you plan to adapt some real world scenarios in these tests in the near future.