1,623
edits
Perceived Performance: Difference between revisions
no edit summary
mNo edit summary |
No edit summary |
||
| Line 30: | Line 30: | ||
* 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. | * 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. | * 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. | |||