Perceived Performance: Difference between revisions

Jump to navigation Jump to search
Line 27: Line 27:
** Change all progress bars in Firefox to use an easing function that automatically biases progress to appear slower at the beginning and faster at the end ([http://www.azarask.in/blog/post/hacking-memory/ aza])
** Change all progress bars in Firefox to use an easing function that automatically biases progress to appear slower at the beginning and faster at the end ([http://www.azarask.in/blog/post/hacking-memory/ aza])
** Use a 1 pixel pulsing progress bar at the bottom of the location bar to denote progress in addition to activity (safari 3 style, but not as heavy).
** Use a 1 pixel pulsing progress bar at the bottom of the location bar to denote progress in addition to activity (safari 3 style, but not as heavy).
** More incremental layout
* Perception of when web page is "done" loading or "done enough" for interaction
* Perception of when web page is "done" loading or "done enough" for interaction
** De-emphasize the throbber and loading indicators once content is visible
** De-emphasize the throbber and loading indicators once content is visible
** Reduce amount of info shown in status bar while a page is loading (hostnames from which scripts are being fetched, etc).
** Reduce amount of info shown in status bar while a page is loading (hostnames from which scripts are being fetched, etc).
** Less incremental layout: except on very slow pages, show content only once layout is stable, so users don't get in the habit of waiting for the activity indicator to go away.
* Optimistic use of cache
* Optimistic use of cache
** Show cached stylesheets and images in addition to sending a (possibly delayed) if-modified-since request
** Show cached stylesheets and images in addition to sending a (possibly delayed) if-modified-since request
Confirmed users
729

edits

Navigation menu