Add-ons
To try the thousands of add-ons available here, download Mozilla Firefox, a fast, free way to surf the Web!
CloseWelcome to Firefox Add-ons.
Choose from thousands of extra features and styles to make Firefox your own.
Close
lori (Life-of-request info) 0.2.0.20080521.1-signed.1-signed.1-signed Requires Restart
by Hung Le
'lori' can tell you how long it takes to load
a page. Useful for web developers who are working on profiling, optimizing a web site.
![[Warning]](https://addons.cdn.mozilla.net/static/img/developers/test-warning.png?b=cf430cf0-59494da8)
Permissions
This add-on is not compatible with your version of Firefox because of the following:
About this Add-on
Regarding Firefox 4 support: please see the section Developer Comments below.
The plugin will add a status bar at the bottom right corner of Firefox and will display:
* TTFB: how long it took to see the first byte from remote server (from click to first byte received). This value gives a rough estimate on when the browser can start laying out the content.
* TTC: how long it took to display the page (from click to complete drawing of the page)
* Page size (number of bytes used to display the page): this value includes both bytes fetched from network and bytes fetched from the browser's cache.
* Number of requests: number of requests used to fetch the page's content (images, style-sheet, javascript ....). Again, this value include both network requests and cache requests.
Notes: that the above stat is only updated when a page is completely displayed (the progress bar is no longer displayed).
Tips
Some rule-of-thumbs on how to interpret/compare these metrics:
* For TTFB, shorter is better. Even for page that is large, a short TTFB (less then .5 sec) allows the browser opportunity to layout the page content as soon as possible. This can enhance the user's perception of responsiveness.
* TTC, obviously shorter is better. The current general agreement is that anything above the range of 7-10 seconds are perceived by user as slow.
* Page size, smaller is better. Most fast sites seem to max out around 75KB per page. Anything above 100KB tends to appear sluggish.
* Number of requests, smaller is better. Nowaday, with HTTP persitent widely supported, the cost of fetching another request no longer significant. But keep an eye for extreme cases (50+). This value tends to correlates well with the page size (large number of request -> large page size).
Keywords: timing, profile, optimize, stopwatch, measure page, http request
The plugin will add a status bar at the bottom right corner of Firefox and will display:
* TTFB: how long it took to see the first byte from remote server (from click to first byte received). This value gives a rough estimate on when the browser can start laying out the content.
* TTC: how long it took to display the page (from click to complete drawing of the page)
* Page size (number of bytes used to display the page): this value includes both bytes fetched from network and bytes fetched from the browser's cache.
* Number of requests: number of requests used to fetch the page's content (images, style-sheet, javascript ....). Again, this value include both network requests and cache requests.
Notes: that the above stat is only updated when a page is completely displayed (the progress bar is no longer displayed).
Tips
Some rule-of-thumbs on how to interpret/compare these metrics:
* For TTFB, shorter is better. Even for page that is large, a short TTFB (less then .5 sec) allows the browser opportunity to layout the page content as soon as possible. This can enhance the user's perception of responsiveness.
* TTC, obviously shorter is better. The current general agreement is that anything above the range of 7-10 seconds are perceived by user as slow.
* Page size, smaller is better. Most fast sites seem to max out around 75KB per page. Anything above 100KB tends to appear sluggish.
* Number of requests, smaller is better. Nowaday, with HTTP persitent widely supported, the cost of fetching another request no longer significant. But keep an eye for extreme cases (50+). This value tends to correlates well with the page size (large number of request -> large page size).
Keywords: timing, profile, optimize, stopwatch, measure page, http request
