Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
Perceived Performance: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Sam Hasler (talk | contribs) (→Awesomebar: Awesomebar look for suggestions when Fx not in focus) |
No edit summary |
||
| Line 6: | Line 6: | ||
* Startup order, what tasks are performed on startup, and is there anything we can defer in order to make the startup experience faster? | * 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 :( | ||
* Checkbox: "Start Firefox when I start | * Checkbox: "Start Firefox when I start [OS]". So I can turn on my computer, go do something else, and return to find it actually ready. | ||
* 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). | * 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). | ||
* A splash screen could alleviate the issue of users not knowing whether their initial double-click to launch Firefox was successful, and inadvertently slowing down startup by making Firefox open ''two'' | ** But what about users who restart Firefox because it's acting weird or in a loop? If it hung around, the command to restart would just reinvoke the broken copy. | ||
* A splash screen could alleviate the issue of users not knowing whether their initial double-click to launch Firefox was successful, and inadvertently slowing down startup by making Firefox open ''two'' windows. | |||
** This would only make a difference if new window time was a significant component of startup time. And anyway, it's the OSes job to indicate whether or not an application-start action was successful. (E.g. on Mac, the Dock icon bounces.) | |||
* Newly opened and currently selected tabs should have higher priority than other loading in background (from previous session). Additionally most-visited websites and nearby tabs could also have some priority boost (I'm talking about >10 or >20 open tabs scenario). | * Newly opened and currently selected tabs should have higher priority than other loading in background (from previous session). Additionally most-visited websites and nearby tabs could also have some priority boost (I'm talking about >10 or >20 open tabs scenario). | ||
| Line 45: | Line 47: | ||
** Based on frequent sequences of clicks | ** Based on frequent sequences of clicks | ||
** Based on hovering over links | ** Based on hovering over links | ||
*** -- Discussion of these issues [http://weblogs.mozillazine.org/gerv/archives/2009/05/mouseover_prefetch.html here]; consensus is that we can't. | |||
* Promote AdBlock | * Promote AdBlock | ||
* Open a lot of links with images (e.g. entire PhD Archive). Firefox loads all HTML files first, but no images at all. I have to wait a long time before the first tab finishes. Firefox should move http requests for the current tab up the request-queue. | * Open a lot of links with images (e.g. entire PhD Archive). Firefox loads all HTML files first, but no images at all. I have to wait a long time before the first tab finishes. Firefox should move http requests for the current tab up the request-queue. | ||