| Site Analysis Report (Sample) |
| |
| Submission Information |
 |
| |
| Report ID: | 3 |
Printer Friendly
|
| Submitted: | Jan 31, 2002 02:02 GMT |
| URL: | http://www.eff.org |
| Depth: | 5 |
| Bandwidth: | 256 Kbit |
| Max Transfer: | 50 Megabytes |
|
| |
| Report Contents |
 |
| | Report Summary |
| | Mime Type Summary |
| | Cache Analysis |
| | Page Content Analysis |
| | Server Load Analysis |
| | User Response Analysis |
| | Broken Links |
| | Missing Images & Inline Content |
| | Itemized List of Requests |
| | Itemized Page Analysis |
| | Appendix A: Terms & Definitions |
| |
| Report Summary |
 |
|
| Analysis started: | Jan 31, 2002 02:02 GMT |
| Analysis completed: | Jan 31, 2002 02:15 GMT |
| Duration of crawl: | 12 minutes 19 seconds |
| Data Transferred: |
51,515,164 bytes. |
| Files downloaded: | 648 |
| Files failed to download: | 21 |
|
| |
| Mime Type Summary |
 |
| | Mime Type |  # Files | Data Xfer | Avg size |
| text/html | 476 | 18731817 | 39352 |
| image/gif | 48 | 116055 | 2417 |
| application/pdf | 13 | 11848003 | 911384 |
| image/jpeg | 14 | 1292067 | 92290 |
| image/png | 1 | 108 | 108 |
| text/css | 4 | 39649 | 9912 |
| text/plain | 85 | 2437234 | 28673 |
| image/tiff | 6 | 17048947 | 2841491 |
|
| |
| Cache Analysis |
 |
| | Cache Analysis determines what
percentage of a page's data is retrieved from the browser's local cache
instead of requiring a request from the remote server.
Readers are cautioned when analyzing these numbers to pay careful attention
to what they can mean: Too little caching, and you may have inline content
such as images arranged in a fashion to prevent caching. Too much caching,
and you may have too many images being used that can slow down the delivery
time of your pages for users that first visit your web pages.
|
|  |
| |
| Page Content Analysis |
 |
| | Page Content Analysis provides
a view of the distribution of page sizes, and what makes up the content
of those pages.
|
|  |
| |
| Server Load Analysis |
 |
|
Based on the size of various web pages, and the amount of caching that a
browser would do as a user visits your site, the following section illustrates
the number of page views/second that can be handled by your server for a
variety of bandwidth configurations.
Please note that bandwidth is only one of a number of perfomance
limiting factors.
|
| |
| |
| Pages/Second Delivery Capability |
| | Server Bandwidth Configurations |
| | 64 Kb | 128 Kb | 512 Kb | 1.544 Mb | 10 Mb |
| Largest page (5760462 bytes) | 0.0 | 0.0 | 0.0 | 0.0 | 0.2 |
| Largest page less cache (5760462 bytes) | 0.0 | 0.0 | 0.0 | 0.0 | 0.2 |
| Home Page (99300 bytes) | 0.1 | 0.1 | 0.5 | 1.6 | 10.3 |
| Average page (91770 bytes) | 0.1 | 0.1 | 0.6 | 1.7 | 11.2 |
| Average page less cache (85640 bytes) | 0.1 | 0.2 | 0.6 | 1.8 | 12.0 |
| Smallest page (0 bytes) | N/A | N/A | N/A | N/A | N/A |
| Smallest page less cache (0 bytes) | N/A | N/A | N/A | N/A | N/A |
| Legend | |
 | Pages of the specified size with the specified bandwidth will take longer than 8 seconds to load. This may result in customers leaving your site. |
 | If more than one person at a time requests a page of this size from your server, the pages will take longer than 8 seconds to be served out. This may result in customers leaving your site. |
 | Page load times are likely to be less than 8 seconds unless your server is experiencing traffic exceeding 10 pages/minute on an ongoing basis. |
|
|
| | "Less Cache" means that only
that component of the page that would be loaded remotely by the browser is
taken into account, based on the browser's own caching mechanisms. It
does not account for any caching servers that may be located between
the user's browser and your web server. Furthermore, the exact amount of
caching that is done by the browser is dependent on the order of the
pages visited. The order of pages retrieved is shown in the section
Itemized List of Requests. |
| |
| User Response Time Analysis |
 |
|
Based on the size of various web pages, and the amount of caching that a
browser would do as a user visits your site, the following section illustrates
how long a user would have to wait for different pages to be loaded, given
different user connectino speeds.
|
| |
| |
| Page Load Time |
| | User Bandwidth Configurations |
| | 33.6 Kb | 56 Kb | 128 Kb | 512 Kb | 1 Mb |
| Largest page (5760462 bytes) | 1704.7 | 1172.0 | 439.5 | 109.9 | 54.9 |
| Largest page less cache (5760462 bytes) | 1704.7 | 1172.0 | 439.5 | 109.9 | 54.9 |
| Home Page (99300 bytes) | 29.4 | 20.2 | 7.6 | 1.9 | 0.9 |
| Average page (91770 bytes) | 27.2 | 18.7 | 7.0 | 1.8 | 0.9 |
| Average page less cache (85640 bytes) | 25.3 | 17.4 | 6.5 | 1.6 | 0.8 |
| Smallest page (0 bytes) | N/A | N/A | N/A | N/A | N/A |
| Smallest page less cache (0 bytes) | N/A | N/A | N/A | N/A | N/A |
| Legend | |
 | Load times exceeding 8 seconds have a high likelihood of being aborted by the user, causing them to leave your site. |
 | Load times exceeding 4 seconds may in the long run cause you to lose traffic, as visitors find more responsive sites elsewhere. |
 | Load times of less than 4 seconds are good. |
|
|
| | "Less Cache" means that only
that component of the page that would be loaded remotely by the browser is
taken into account, based on the browser's own caching mechanisms. |
| |
| Broken Links |
 |
| | We found a broken link on the following pages: |
| http://www.eff.org/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/LINK_REL/howtouse.html |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/LINK_REL/howtouse.html |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/LINK_REL/howtouse.html |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/LINK_REL/howtouse.html |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/br/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/privnow/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/privnow/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/privnow/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/privnow/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/privnow/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/Legal/active_legal.html |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/news/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/effector/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/effector/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/effector/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/effector/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/opportunities/ |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/contact.html |
| |
| |
| |
| | We found a broken link on the following pages: |
| http://www.eff.org/IP/Internet_address_disputes/Kremen_v_NSI/20020123_eff_kremen_pr.html |
| |
| |
| |
| |
| Missing Images & Inline Content |
 |
| We found no missing inline content. |
| |
| Itemized List of Requests |
 |
|
The complete list of pages retrieved is available in the
report supplement.
|
| |
| Itemized Page Analysis |
 |
|
The complete list of pages retrieved is available in the
report supplement.
|
| |
| Appendix A: Terms & Definitions |
 |
- Inline Content
Inline content is content that most browsers will retrieve in order to fully
display a web page. Images are the most common form of inline content, but
other forms include HTML pages (frames, iframes), css files (stylesheets),
Shockwave/Flash files, JavaScript libraries, and more.
Occasionally, a component may be reported both as inline content and
as a separate link. This happens most often when Framed content is missing,
and referred to both in a framed window as well as a separate link.
|