Every page on version one is slow to load. I've tried reducing the rows of data returned to 10, and it's still slow. We recently switched from a shared server to a dedicated server to run Version One with no visible improvement.
Why does this matter?
During sprint planning, I wind up having to refresh or reload the page anywhere from 50-100 times depending on the tasks and stories we're editing. I used Fiddler2 to check the load time on the page. Each page load, even if coming from cache, is at least 5 seconds. It's often closer to 8 seconds. So, let's say that I refresh the page 100 times in a typical sprint planning session. That's 500-800 seconds I and my entire team are staring at the screen waiting for it to refresh. That's 8-13 MINUTES we're staring at the screen waiting for it to refresh. With 6 of us in the meeting, that quickly multiplies into a lot of lost productivity - something like 1-1.25 hours of lost productivity because of poor site design.
What do I mean poor site design?
On the member planning page, there are 9 separate requests for CSS files, which could easily be stitched together server-side into a single file. Those 9 requests took a total of 1.5 seconds just to load the styles.
Then there are at least 20 separate requests for javascript files. Sometimes those are a bit harder to stitch together, so I'm not suggesting they go to a single request, but 20 requests is ludicrous. Those 20 requests do happen at the same time as the CSS files in this case, but they take a total of just over 2 seconds, extending the wait time for the page another ~0.5 seconds past the time we waited for the 9 CSS files.
The the images - I lost count at 40 images, each a separate request. Version One, you need to learn about sprites and leverage them heavily. Buttons and curves can be done with CSS and/or jquery.
You need to get YSlow or assess page load time with something more scientific than this, but page load time is long overdue. I think VersionOne is an AWESOME product, but every day I use it, I get more and more frustrated by the unnecessary delays. VersionOne is an impediment to my and my team's productivity. Please do something about it!
Thanks for your consideration.
by: Robert B. | over a year ago | User Interface
Comments
I concur. running with firebug shows 10-20 second load times quite common. It makes the service borderline unusable. I cannot comment on it's awesomeness as this load time issue destroys any good will I have towards this product.
On Spring 2011, CSS alone on My Work page is > 300K. This is probably a large factor in the increased load times.
As a Scrum Master, it is essential that the VersionOne interface be responsive and easy to use. Slow page loads and noticeable lags when saving state detract from the user experience and are a barrier to user adoption.
Yes, I agree.
The slow response and delay in page load times is particularly visible and frustrating to our remote users who are not physically in the same office space.
We made some changes to our server configuration as suggested by V1 support but yet it does not meet the desired page load response times....1-2 seconds.
slowest productivity app I regularly use. Other than that, it's great - but the performance is surprisingly weak in this regard.
We did a number of performance enhacements over time a while back. Testing and feedback over time has showed us that worked, so we're closing this one out.