Write an Internet Explorer extension/add-on that can measure the time spent fetching and rendering web pages as the user browses from page to page.
Results need to be displayed in a window and also need to be copied to the clipboard.
## Deliverables
Here's what I envision?€?
The user installs this new extension into Internet Explorer and gets another icon showing up somewhere on one of the Internet Explorer window (very similar to how Firebug and YSlow show up in Firefox).
The user clicks on that icon and a new window opens up (ideally appearing as a detached window which can remain open as you browse around). In that window you will see a "Reset Statistics" button, a "Copy to clipboard" button, and an area for the results to be output.
Each time you browse to a new page, it will record the elapsed time between the start of the new page fetch and when rendering is complete. It will automatically update the display window with a new row of data, showing something like this after 4 clicks:
| Seconds | Page URL |
| 1.08 | <[login to view URL]> |
| 3.05 | <[login to view URL]> |
| 2.73 | <[login to view URL]> |
| 1.08 | <[login to view URL]> |
| --------- | |
| 9.52 | Total for 4 pages |
Other notes:
- It will not record the time to full document download; it will only record the time to when rendering is complete (so that any pre-fetching a web page does won't be reported as a speed penalty).
- If you press "reset" the stats all clear.
- If you press "copy", it copies the data into the clipboard in a text format that can easily be pasted into Excel (that's why I didn't put any units beside the numbers in the seconds column).
- New data is added (and totaled) for every new page you visit until you hit reset. New stuff goes at the bottom of the list.
If possible, also display the time for the most recent page near the icon/toolbar/whatever, regardless of whether the stats window is open or not.
Bidders on this project have been asking for clarification of when timing should begin and when it should end. Timing should begin when Internet Explorer starts to fetch a new page (probably because the user clicked on a link, typed in a URL, or refreshed a page).
Timing should end when the web page javascript "onload" events occurs. Time spent executing onload events should not be included. Here's a timing example of the google homepage: [login to view URL]
The vertical blue line at .403 seconds is what I'm interested in having measured as the end time.
I'm willing to pay more for someone who can finish this sooner.
* * *This broadcast message was sent to all bidders on Friday Sep 5, 2008 10:51:28 AM:
Bidders on this project have been asking for clarification of when timing should begin and when it should end. Timing should begin when Internet Explorer starts to fetch a new page (probably because the user clicked on a link, typed in a URL, or refreshed a page). Timing should end when the web page javascript "onload" events occurs. Time spent executing onload events should not be included. Here's a timing example of the google homepage: [login to view URL] The vertical blue line at .403 seconds is what I'm interested in having measured as the end time.