Perceived Performance: Difference between revisions

Jump to navigation Jump to search

Perceived Performance (view source)

Revision as of 23:37, 25 July 2009

953 bytes added ,  25 July 2009
Organize into sections and add some ideas
No edit summary
(Organize into sections and add some ideas)
Line 2: Line 2:


Add your ideas for things we should look at to make Firefox feel faster below:
Add your ideas for things we should look at to make Firefox feel faster below:
* Faster timeouts on pages that don't load.
 
* Make "This is embarrassing..." (change the message, obvi) the default upon restart, so users can choose which tabs to re-establish
== Firefox startup ==
* Watchdog RAM usage and throw up warning when too many tabs are open
* Startup order, what tasks are performed on startup, and is there anything we can defer in order to make the startup experience faster?
* Implement a preloader in the system tray ([http://sourceforge.net/projects/ffpreloader/ this project] has been abandoned since 2005 and breaks in FF 3.5). There used to be a preloader in the Mozilla Suite, and you removed it in Firefox :(
* Implement a preloader in the system tray ([http://sourceforge.net/projects/ffpreloader/ this project] has been abandoned since 2005 and breaks in FF 3.5). There used to be a preloader in the Mozilla Suite, and you removed it in Firefox :(
* Make the throbber faster :p (we honestly do it every release)
* Keep firefox running for a moment after close for the set of users who close and reopen the application in order to do a search (because the start page has a search field, and they don't know about the search bar, location bar, or home button).
 
== Loading web pages ==
* Web pages that load very slowly
** Faster timeouts on pages that don't load at all
** Time out script loads, especially third-party script loads, more readily than page loads
** Increase the amount of visual change when loading a slow page, for instance transition to a large water mark style throbber that appears in the center of the content area if no information has loaded yet
** Offer to keep trying for me every few hours
** Offer coral cache link
** Show traceroute results while the page continues to not load
** Nudge users toward using "open link in background tab" more.
* Perception of how fast Firefox is working
** Make the throbber faster :p (we honestly do it every release)
** 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).
* Perception of when web page is "done" loading or "done enough" for interaction
** 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).
* Optimistic use of cache
** Show cached stylesheets and images in addition to sending a (possibly delayed) if-modified-since request
** Use cached image ''sizes'' even when we can't use the actual cached image
** Cache whether the page layout required a scrollbar
** Use cached page to fire off requests for scripts and stylesheets (fewer round-trips needed for initial dipslay of the page)
** Show entire page from cache, and then fade to a copy loaded off of the network once it is ready
* Preload web pages
** Based on time of day
** Based on frequent sequences of clicks
** Based on hovering over links
* Promote AdBlock
 
== Scrolling web pages ==
* Implement the OS X scrolling model for our Windows and Linux builds of Firefox ([https://bugzilla.mozilla.org/show_bug.cgi?id=462809 bug 462809])
* Implement the OS X scrolling model for our Windows and Linux builds of Firefox ([https://bugzilla.mozilla.org/show_bug.cgi?id=462809 bug 462809])
* Use a real time strategy game style scroll box in the content area, so you can quickly move around a page just by moving the mouse
* Use a real time strategy game style scroll box in the content area, so you can quickly move around a page just by moving the mouse
* Subtle but smooth graphics accelerated back and forward animations, like a very very slight fade and pane)
 
* Marking menu on downclick (to something on the page that doesn't take the focus) for back and forward navigation, execute the action on hover instead of upclick so that it feels extremely responsive.  The user needs to hover back to center to cancel.  ([http://people.mozilla.com/~faaborg/files/daf/pieNav.png mockup of the interface] )
== Too many tabs ==
* Increase the amount of visual change when loading a slow page, for instance transition to a large water mark style throbber that appears in the center of the content area if no information has loaded yet
* Use less RAM when many tabs are open
* Keep firefox running for a moment after close for the set of users who close and reopen the application in order to do a search (because the start page has a search field, and they don't know about the search bar, location bar, or home button).
** Warn when too many tabs are open, or when too much RAM has been used.
* 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).
** Drop the DOM of tabs the user has not interacted with?  (Decrease memory use, increase lag when switching to that tab.)
* Make session restore faster with many tabs
** Load the frontmost tab on startup before the others (filed as [https://bugzilla.mozilla.org/show_bug.cgi?id=496458 bug 496458])
** On restart, show a list of tabs Firefox can restore, instead of just restoring them.  (Like we currently do when recovering from a crash.)
* Nudge users toward opening fewer tabs
** Give users a good alternative to ''using open tabs as reminders'', something that works better than bookmarks or copy+pasting URLs into Things
 
== Back and forward ==
* Subtle but smooth graphics accelerated back and forward animations, like a very very slight fade and pane
* Pref to turn off the "disable bfcache if page has unload handler" heuristic (similar to Opera)
* Show context menu on mousedown on more platforms
* Pie context menu ([http://people.mozilla.com/~faaborg/files/daf/pieNav.png mockup of the interface] )
** Show previous page when ''hovering'' over the Back command in the context menu, now that Back is not on the way to the other menu items
 
== Awesomebar ==
* Don't require the user to hit the down arrow in order to access the first result in the awesome bar (complicated, details in [https://bugzilla.mozilla.org/show_bug.cgi?id=410837 bug 410837])  
* Don't require the user to hit the down arrow in order to access the first result in the awesome bar (complicated, details in [https://bugzilla.mozilla.org/show_bug.cgi?id=410837 bug 410837])  
* Give the awesome bar the focus on open so you don't have to focus it yourself before navigating to a particular location
* Give the awesome bar the focus on open so you don't have to focus it yourself before navigating to a particular location
* Quickly load pages out of cache and then fade to a copy loaded off of the network once it is ready (also, display a greyed out version of the cache page with highlighted form fields when prompting the user if they want to ressend information)
* Don't show the progress spinner for the address bar until 200-300ms have passed (it currently appears instantly, and makes it feel like you're waiting for results).
* Use frecency and adaptive learning to proactively preload pages we expect the user to visit (at a time of day, in a common sequence, etc.)
* Move awesome bar loading to occur before most other async tasks that happen, Almost always when I open a new firefox the urlbar is frozen (I type some chars and nothing is shown). This gives a very slugish impression. (santagada)
 
== Update ==
* Install updates with a background process so updating doesn't delay the next startup.
* Install add-on updates automatically too.
 
== Other ==
* Extend the password manager to allow for automatic log ins (with feedback that this is happening)
* Extend the password manager to allow for automatic log ins (with feedback that this is happening)
* Install updates with a background process so updating doesn't impact start up time on the next start up
* Load the frontmost tab on startup before the others (filed as [https://bugzilla.mozilla.org/show_bug.cgi?id=496458 bug 496458])
* Don't show the progress spinner for the address bar until 200-300ms have passed (it currently appears instantly, and makes it feel like you're waiting for results).
* Color change impact when creating a new tab
* Color change impact when creating a new tab
* Startup order, what tasks are performed on startup, and is there anything we can defer in order to make the startup experience faster?
* Switching tabs is not instantaneous when Firefox is busy (e.g. loading complex or multiple web pages)
* Switching tabs while loading several tabs seems slow
* Deleting history items has lag. Make them dissapear when delete is pressed, then delete them.
*Deleting history items has lag. Make them dissapear when delete is pressed, then delete them.
* Move awesome bar loading to occur before most other async tasks that happen, Almost always when I open a new firefox the urlbar is frozen (I type some chars and nothing is shown). This gives a very slugish impression. (santagada)
* Related to above (switching tabs), allow/improve tab switching when loading particularly intensive pages. (eg. FF ''appears'' to lock up at times when loading http://fixoutlook.org/ as it's contending with many images, etc).
* Friendlier looking error pages. Most people blame Firefox and not the site causing an issue when they see an error page. Is there a standard that must be followed whereas error pages must be presented to look so cold and raw? A little style and color psychology might help to ease the frustration that a user is feeling when they can't get to where they are trying to go.
* Tough one but it would be great if something could be done to reduce the great amount of info that is displayed in the status bar while a site/page is loading. I sometimes wonder why I have cookies enabled at all and why connections to 10 other sites are necessary when I see everything that a page is loading.
* Closing the (only) Firefox window with the close button ("X" on Windows and Linux, red dot on Mac) is instantaneous, but pressing Ctrl+Q makes Firefox hang completely for a second while still showing the window. Ctrl+Q should also instantly close the (current?) window so it disappears from view before it silently shuts down completely in the background.
* Closing the (only) Firefox window with the close button ("X" on Windows and Linux, red dot on Mac) is instantaneous, but pressing Ctrl+Q makes Firefox hang completely for a second while still showing the window. Ctrl+Q should also instantly close the (current?) window so it disappears from view before it silently shuts down completely in the background.
* Friendlier looking error pages. Most people blame Firefox and not the site causing an issue when they see an error page. A little style and color psychology might help to ease the frustration that a user is feeling when they can't get to where they are trying to go.
Jesse
Confirmed users
729

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/157532"

Navigation menu