Performance Report:
Page URL: http://www.youtube.com/
Page Title: YouTube
Report Generated on: February 08 2013 20:01:36. CST
Page Load Time: 2.10 sec
Page Size: 1,058.50 kb
Number of Requests: 36
HTTP Status Code: 200
Number of Hops:
Page Size: 1,058.50 kb
Number of Requests: 36
HTTP Status Code: 200
Number of Hops:
Performance Analysis
Showing Performance Analysis and Tunig Tips
- http://ad.doubleclick.net/activity;src=3163378;met=1;v=1;pid=94134034;aid=268279062;ko=0;cid=52690343;rid=52644156;rv=2;×tamp=1360375274098;eid1=9;ecn1=1;etm1=0;
- http://s0.2mdn.net/879366/iframe_buster_200_18.js
- [native code]
- http://clients1.google.com/generate_204
- http://s.ytimg.com/yts/jsbin/www-searchbox-vflJnRubz.js
- [native code]
- http://s.ytimg.com/yts/img/icons/close-vflrEJzIW.png
- http://s.ytimg.com/yts/jsbin/www-searchbox-vflJnRubz.js
- [native code]
- http://s0.2mdn.net/ads/richmedia/studio/23115778/23115781_1359624763567_BackupImage.jpg
- http://s0.2mdn.net/879366/iframe_buster_200_18.js
- [native code]
- http://www.gstatic.com/inputtools/images/tia.png
- http://s.ytimg.com/yts/jsbin/www-searchbox-vflJnRubz.js
- [native code]
- http://s.ytimg.com/yts/jsbin/www-core-vflT0ckX0.js (182KiB)
- http://s.ytimg.com/yts/jsbin/www-home-vfl5A62lM.js (62.1KiB)
- http://s.ytimg.com/yts/jsbin/www-guide-vflCYmjpq.js (39.8KiB)
- http://ad-g.doubleclick.net/N4061/adi/com.ythome/_default;sz=970x250;tile=1;plat=pc;dc_dedup=1;kbsg=HPUS130208;kcr=us;kga=-1;kgg=-1;klg=en;kmyd=ad_creative_1;ord=2625405695289373? (4.8KiB of inline JavaScript)
- http://www.youtube.com/ (2.5KiB of inline JavaScript)
- http://ad-g.doubleclick.net/N6762/adi/mkt.ythome_1x1/;sz=1x1;tile=3;plat=pc;dc_dedup=1;kcr=us;kga=-1;kgg=-1;klg=en;kmyd=ad_creative_3;ord=5093203000724316? (2.4KiB of inline JavaScript)
- http://www.youtube.com/ (2 reflows)
- http://s.ytimg.com/yts/jsbin/www-core-vflT0ckX0.js (1 reflows)
- http://i1.ytimg.com/i/huLeaTGRcfzo0UjL-2qSbQ/1.jpg (6 hours)
- http://i1.ytimg.com/i/l8dMTqDrJQ0c8y23UBu4kQ/1.jpg (6 hours)
- http://i1.ytimg.com/li/PvDBPPFfuaM/default.jpg (6 hours)
- http://i1.ytimg.com/li/hfZhJdhTqX8/default.jpg (6 hours)
- http://i1.ytimg.com/li/p-Rdqh3z4Uc/default.jpg (6 hours)
- http://i1.ytimg.com/li/tnHdj3df7iM/default.jpg (6 hours)
- http://i1.ytimg.com/vi/0IJoKuTlvuM/default.jpg (6 hours)
- http://i1.ytimg.com/vi/4AmnabttACI/mqdefault.jpg (6 hours)
- http://i1.ytimg.com/vi/lLA7dQ-uxR0/hqdefault.jpg (6 hours)
- http://i1.ytimg.com/vi/lWA2pjMjpBs/default.jpg (6 hours)
- http://i1.ytimg.com/vi/tWXh_4GjxK8/mqdefault.jpg (6 hours)
- http://i2.ytimg.com/i/ULkRHBdLC5ZcEQBaL0oYHQ/1.jpg?v=50bd2bea (6 hours)
- http://i2.ytimg.com/i/eTKJSW1NTAkf27nNmjWt5A/1.jpg (6 hours)
- http://i2.ytimg.com/i/qnbDFdCpuN8CMEg0VuEBqA/1.jpg (6 hours)
- http://i2.ytimg.com/vi/-t6cxIeCIjE/mqdefault.jpg (6 hours)
- http://i2.ytimg.com/vi/98NwW0WuQIw/mqdefault.jpg (6 hours)
- http://i2.ytimg.com/vi/9bZkp7q19f0/default.jpg (6 hours)
- http://i2.ytimg.com/vi/AMpZ0TGjbWE/default.jpg (6 hours)
- http://i2.ytimg.com/vi/MG2HPtbV-80/default.jpg (6 hours)
- http://i2.ytimg.com/vi/QK8mJJJvaes/default.jpg (6 hours)
- http://i2.ytimg.com/vi/il21FZu-IUY/mqdefault.jpg (6 hours)
- http://i2.ytimg.com/vi/qmMbm78sEB4/mqdefault.jpg (6 hours)
- http://i3.ytimg.com/i/ZWNlftHmjE3WdpKKULeLtg/1.jpg (6 hours)
- http://i3.ytimg.com/vi/Ftm5tN21IJw/default.jpg (6 hours)
- http://i3.ytimg.com/vi/ZAmwawDjDaQ/default.jpg (6 hours)
- http://i3.ytimg.com/vi/bxA4rmdflCA/default.jpg (6 hours)
- http://i3.ytimg.com/vi/jAptCdalzug/mqdefault.jpg (6 hours)
- http://i4.ytimg.com/i/czhp4wznQWonO7Pb8HQ2MQ/1.jpg (6 hours)
- http://i4.ytimg.com/i/kzRDjtq4ngMADh45j2KsJQ/1.jpg (6 hours)
- http://i4.ytimg.com/li/7Dr1BKwqctY/default.jpg (6 hours)
- http://i4.ytimg.com/vi/OpQFFLBMEPI/mqdefault.jpg (6 hours)
- http://i4.ytimg.com/vi/kZ9UQoV5JFQ/default.jpg (6 hours)
- http://i4.ytimg.com/vi/oFR4L6GegXA/mqdefault.jpg (6 hours)
- Minifying http://www.youtube.com/ could save 806B (6% reduction) after compression.
- Minifying http://ad-g.doubleclick.net/N4061/adi/com.ythome/_default;sz=970x250;tile=1;plat=pc;dc_dedup=1;kbsg=HPUS130208;kcr=us;kga=-1;kgg=-1;klg=en;kmyd=ad_creative_1;ord=2625405695289373? could save 412B (12% reduction) after compression.
- Minifying http://s.ytimg.com/yts/jsbin/www-core-vflT0ckX0.js could save 470B (1% reduction) after compression.
- http://www.google.com/pagead/drt/ui
- https://googleads.g.doubleclick.net/pagead/drt/si?p=CAA&ut=AFAKxlQAAAAAURWxbqAKlfsDVUR7Fg8KlEnJagF3aHc_
- Losslessly compressing http://pagead2.googlesyndication.com/simgad/14037213758874105556 could save 12.7KiB (99% reduction).
- Losslessly compressing http://s0.2mdn.net/ads/richmedia/studio/23115778/23115781_1359624763567_BackupImage.jpg could save 935B (2% reduction).
- Losslessly compressing http://i4.ytimg.com/i/czhp4wznQWonO7Pb8HQ2MQ/1.jpg could save 898B (10% reduction).
- Losslessly compressing http://i4.ytimg.com/i/kzRDjtq4ngMADh45j2KsJQ/1.jpg could save 782B (9% reduction).
- Losslessly compressing http://i2.ytimg.com/i/eTKJSW1NTAkf27nNmjWt5A/1.jpg could save 344B (5% reduction).
- http://i2.ytimg.com/i/ULkRHBdLC5ZcEQBaL0oYHQ/1.jpg?v=50bd2bea
- http://i1.ytimg.com/vi/4AmnabttACI/mqdefault.jpg is resized in HTML or CSS from 320x180 to 189x106. Serving a scaled image could save 9.5KiB (65% reduction).
- http://i4.ytimg.com/i/czhp4wznQWonO7Pb8HQ2MQ/1.jpg is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 9.2KiB (95% reduction).
- http://i4.ytimg.com/i/kzRDjtq4ngMADh45j2KsJQ/1.jpg is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 8.4KiB (95% reduction).
- http://i1.ytimg.com/vi/tWXh_4GjxK8/mqdefault.jpg is resized in HTML or CSS from 320x180 to 189x106. Serving a scaled image could save 8KiB (65% reduction).
- http://i2.ytimg.com/i/eTKJSW1NTAkf27nNmjWt5A/1.jpg is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 7.6KiB (95% reduction).
- http://i4.ytimg.com/vi/oFR4L6GegXA/mqdefault.jpg is resized in HTML or CSS from 320x180 to 189x106. Serving a scaled image could save 7.5KiB (65% reduction).
- http://i2.ytimg.com/vi/il21FZu-IUY/mqdefault.jpg is resized in HTML or CSS from 320x180 to 189x106. Serving a scaled image could save 7.5KiB (65% reduction).
- http://i1.ytimg.com/vi/lLA7dQ-uxR0/hqdefault.jpg is resized in HTML or CSS from 480x360 to 370x277. Serving a scaled image could save 7.4KiB (41% reduction).
- http://i2.ytimg.com/vi/98NwW0WuQIw/mqdefault.jpg is resized in HTML or CSS from 320x180 to 189x106. Serving a scaled image could save 7KiB (65% reduction).
- http://i4.ytimg.com/vi/OpQFFLBMEPI/mqdefault.jpg is resized in HTML or CSS from 320x180 to 165x93. Serving a scaled image could save 6.9KiB (73% reduction).
- http://i2.ytimg.com/vi/-t6cxIeCIjE/mqdefault.jpg is resized in HTML or CSS from 320x180 to 182x102. Serving a scaled image could save 6.6KiB (67% reduction).
- http://i3.ytimg.com/vi/jAptCdalzug/mqdefault.jpg is resized in HTML or CSS from 320x180 to 182x102. Serving a scaled image could save 6.5KiB (67% reduction).
- http://i2.ytimg.com/vi/qmMbm78sEB4/mqdefault.jpg is resized in HTML or CSS from 320x180 to 189x106. Serving a scaled image could save 3.8KiB (65% reduction).
- http://i4.ytimg.com/vi/kZ9UQoV5JFQ/default.jpg is resized in HTML or CSS from 120x90 to 64x48. Serving a scaled image could save 3.4KiB (71% reduction).
- http://i3.ytimg.com/vi/ZAmwawDjDaQ/default.jpg is resized in HTML or CSS from 120x90 to 64x48. Serving a scaled image could save 3.4KiB (71% reduction).
- http://i3.ytimg.com/vi/bxA4rmdflCA/default.jpg is resized in HTML or CSS from 120x90 to 64x48. Serving a scaled image could save 3.4KiB (71% reduction).
- http://i3.ytimg.com/vi/Ftm5tN21IJw/default.jpg is resized in HTML or CSS from 120x90 to 64x48. Serving a scaled image could save 3.3KiB (71% reduction).
- http://i2.ytimg.com/vi/9bZkp7q19f0/default.jpg is resized in HTML or CSS from 120x90 to 64x48. Serving a scaled image could save 3.1KiB (71% reduction).
- http://i4.ytimg.com/li/7Dr1BKwqctY/default.jpg is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 2.9KiB (95% reduction).
- http://i2.ytimg.com/vi/QK8mJJJvaes/default.jpg is resized in HTML or CSS from 120x90 to 64x48. Serving a scaled image could save 2.9KiB (71% reduction).
- http://i1.ytimg.com/li/PvDBPPFfuaM/default.jpg is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 2.8KiB (95% reduction).
- http://i1.ytimg.com/i/l8dMTqDrJQ0c8y23UBu4kQ/1.jpg is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 2.7KiB (95% reduction).
- http://i1.ytimg.com/li/p-Rdqh3z4Uc/default.jpg is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 2.1KiB (95% reduction).
- http://i1.ytimg.com/li/hfZhJdhTqX8/default.jpg is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 2KiB (95% reduction).
- http://i3.ytimg.com/i/ZWNlftHmjE3WdpKKULeLtg/1.jpg is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 1.9KiB (95% reduction).
- http://i2.ytimg.com/i/qnbDFdCpuN8CMEg0VuEBqA/1.jpg is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 1.7KiB (95% reduction).
- http://i1.ytimg.com/li/tnHdj3df7iM/default.jpg is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 1.7KiB (95% reduction).
- http://i1.ytimg.com/i/huLeaTGRcfzo0UjL-2qSbQ/1.jpg is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 1.6KiB (95% reduction).
- http://i2.ytimg.com/i/ULkRHBdLC5ZcEQBaL0oYHQ/1.jpg?v=50bd2bea is resized in HTML or CSS from 88x88 to 18x18. Serving a scaled image could save 1.5KiB (95% reduction).
- http://i1.ytimg.com/vi/lWA2pjMjpBs/default.jpg is resized in HTML or CSS from 120x90 to 64x48. Serving a scaled image could save 1.2KiB (71% reduction).
- http://i1.ytimg.com/vi/4AmnabttACI/mqdefault.jpg
- http://i3.ytimg.com/vi/Ftm5tN21IJw/default.jpg
- http://i3.ytimg.com/vi/ZAmwawDjDaQ/default.jpg
- http://i3.ytimg.com/vi/bxA4rmdflCA/default.jpg
- http://i3.ytimg.com/vi/jAptCdalzug/mqdefault.jpg
- http://i4.ytimg.com/vi/kZ9UQoV5JFQ/default.jpg
- http://i4.ytimg.com/vi/oFR4L6GegXA/mqdefault.jpg
PageSpeed Analysis and Performance Suggestions
| Rule Name | Grade | Severity |
|---|---|---|
| Avoid bad requests | Low | |
| No improvement suggestion available. Good job! | ||
| Avoid a character set in the meta tag | Low | |
| No improvement suggestion available. Good job! | ||
| Avoid CSS @import | Low | |
| No improvement suggestion available. Good job! | ||
| Reduce request serialization | High | |
|
The following requests are serialized. Try to break up the dependencies to make them load in parallel.
The following requests are serialized. Try to break up the dependencies to make them load in parallel.
The following requests are serialized. Try to break up the dependencies to make them load in parallel.
The following requests are serialized. Try to break up the dependencies to make them load in parallel.
The following requests are serialized. Try to break up the dependencies to make them load in parallel.
|
||
| Avoid landing page redirects | Low | |
| No improvement suggestion available. Good job! | ||
| Avoid long-running scripts | Low | |
| No improvement suggestion available. Good job! | ||
| Defer parsing of JavaScript | High | |
|
293.6KiB of JavaScript is parsed during initial page load. Defer parsing JavaScript to reduce blocking of page rendering.
|
||
| Eliminate unnecessary reflows | Medium | |
|
JavaScript that executed in the following resources caused unnecessary reflows. To reduce page render time, modify the JavaScript so it does not cause a reflow:
|
||
| Enable compression | Low | |
| No improvement suggestion available. Good job! | ||
| Inline Small CSS | Low | |
| No improvement suggestion available. Good job! | ||
| Inline Small JavaScript | Low | |
| No improvement suggestion available. Good job! | ||
| Leverage browser caching | High | |
|
The following cacheable resources have a short freshness lifetime. Specify an expiration at least one week in the future for the following resources:
|
||
| Minify CSS | Low | |
| No improvement suggestion available. Good job! | ||
| Minify HTML | Medium | |
|
Minifying the following HTML resources could reduce their size by 1.2KiB (7% reduction).
|
||
| Minify JavaScript | Medium | |
|
Minifying the following JavaScript resources could reduce their size by 470B (1% reduction).
|
||
| Minimize redirects | High | |
|
Remove the following redirect chain if possible:
|
||
| Minimize request size | Low | |
| No improvement suggestion available. Good job! | ||
| Optimize images | High | |
|
Optimizing the following images could reduce their size by 15.6KiB (15% reduction).
|
||
| Optimize the order of styles and scripts | Low | |
| No improvement suggestion available. Good job! | ||
| Prefer asynchronous resources | Low | |
| No improvement suggestion available. Good job! | ||
| Put CSS in the document head | Low | |
| No improvement suggestion available. Good job! | ||
| Remove query strings from static resources | Low | |
|
Resources with a "?" in the URL are not cached by some proxy caching servers. Remove the query string and encode the parameters into the URL for the following resources:
|
||
| Serve resources from a consistent URL | Low | |
| No improvement suggestion available. Good job! | ||
| Serve scaled images | High | |
|
The following images are resized in HTML or CSS. Serving scaled images could save 137.4KiB (72% reduction).
|
||
| Specify a cache validator | High | |
|
The following resources are missing a cache validator. Resources that do not specify a cache validator cannot be refreshed efficiently. Specify a Last-Modified or ETag header to enable cache validation for the following resources:
|
||
| Specify a Vary: Accept-Encoding header | Low | |
| No improvement suggestion available. Good job! | ||
| Specify a character set | Low | |
| No improvement suggestion available. Good job! | ||
| Specify image dimensions | Low | |
| No improvement suggestion available. Good job! | ||
| Combine images into CSS sprites | Low | |
| No improvement suggestion available. Good job! | ||
- s.ytimg.com: 11 components, 366.3K
- i1.ytimg.com: 2 components, 23.4K
- i2.ytimg.com: 2 components, 5.2K
- s0.2mdn.net: 2 components, 100.3K
- pagead2.googlesyndication.com: 1 component, 13.1K
- http://s.ytimg.com/yts/img/icn_loading_animated-vflff1Mjj.gif
- http://s.ytimg.com/yts/imgbin/www-refresh-vflnO-Put.png
- http://i1.ytimg.com/vi/lLA7dQ-uxR0/hqdefault.jpg
- http://i2.ytimg.com/vi/MG2HPtbV-80/default.jpg
- http://i2.ytimg.com/vi/AMpZ0TGjbWE/default.jpg
- http://i1.ytimg.com/vi/0IJoKuTlvuM/default.jpg
- http://s.ytimg.com/yts/img/favicon-vfldLzJxy.ico
- http://s.ytimg.com/yts/img/favicon_32-vflWoMFGx.png
- http://s0.2mdn.net/879366/iframe_buster_200_18.js
- http://s0.2mdn.net/ads/richmedia/studio/23115778/23115781_1359624763567_BackupImage.jpg
- http://www.youtube.com/
- http://s.ytimg.com/yts/cssbin/www-core-vfllMpEC9.css
- http://s.ytimg.com/yts/cssbin/www-home-c4-vflj7s9Ng.css
- http://s.ytimg.com/yts/jsbin/www-core-vflT0ckX0.js
- http://s.ytimg.com/yts/jsbin/www-guide-vflCYmjpq.js
- http://s.ytimg.com/yts/jsbin/www-home-vfl5A62lM.js
- http://ad-g.doubleclick.net/N4061/adi/com.ythome/_default;sz=970x250;tile=1;plat=pc;dc_dedup=1;kbsg=HPUS130208;kcr=us;kga=-1;kgg=-1;klg=en;kmyd=ad_creative_1;ord=9433186424430460?
- http://s0.2mdn.net/879366/iframe_buster_200_18.js
- http://ad-g.doubleclick.net/N6762/adi/mkt.ythome_1x1/;sz=1x1;tile=3;plat=pc;dc_dedup=1;kcr=us;kga=-1;kgg=-1;klg=en;kmyd=ad_creative_3;ord=165044809691607?
- There is a total of 16 inline scripts
- www.youtube.com: 1 component, 13.5K
- s.ytimg.com: 11 components, 366.3K
- i1.ytimg.com: 2 components, 23.4K
- i2.ytimg.com: 2 components, 5.2K
- ad-g.doubleclick.net: 2 components, 16.1K
- s0.2mdn.net: 2 components, 100.3K
- pagead2.googlesyndication.com: 1 component, 13.1K
- googleads.g.doubleclick.net: 1 component, 0.1K
- inline <script> tag #9
- inline <script> tag #10
YSlow Analysis and Performance Suggestions
| Rule Name | Grade | Severity |
|---|---|---|
Make fewer HTTP Requests  Decreasing the number of components on a page reduces the number of HTTP requests required to render the page, resulting in faster page loads. Some ways to reduce the number of components include: combine files, combine multiple scripts into one script, combine multiple CSS files into one style sheet, and use CSS Sprites and image maps. |
High | |
|
This page has 4 external Javascript scripts. Try combining them into one.
|
||
| Use a Content Delivery Network(CDN) User proximity to web servers impacts response times. Deploying content across multiple geographically dispersed servers helps users perceive that pages are loading faster. |
Medium | |
|
There are 18 static components that are not on CDN.
|
||
| Avoid empty src or href Empty src or href attributes can cause multiple problems. This could possibly corrupt user data, waste server computing cycles generating a page that will never be viewed, and in the worst case, cripple your servers by sending a large amount of unexpected traffic. |
High | |
| No improvement suggestion available. Good job! | ||
| Add Expires headers Web pages are becoming increasingly complex with more scripts, style sheets, images, and Flash on them. A first-time visit to a page may require several HTTP requests to load all the components. By using Expires headers these components become cacheable, which avoids unnecessary HTTP requests on subsequent page views. Expires headers are most often associated with images, but they can and should be used on all page components including scripts, style sheets, and Flash. |
High | |
|
There are 10 static components without a far-future expiration date.
|
||
| Compress components with gzip Compression reduces response times by reducing the size of the HTTP response. Gzip is the most popular and effective compression method currently available and generally reduces the response size by about 70%. Approximately 90% of today's Internet traffic travels through browsers that claim to support gzip. |
High | |
|
There are 9 plain text components that should be sent compressed
|
||
| Put CSS at top Moving style sheets to the document HEAD element helps pages appear to load quicker since this allows pages to render progressively. |
Medium | |
| No improvement suggestion available. Good job! | ||
| Put JavaScript at bottom JavaScript scripts block parallel downloads; that is, when a script is downloading, the browser will not start any other downloads. To help the page load faster, move scripts to the bottom of the page if they are deferrable. |
Medium | |
| No improvement suggestion available. Good job! | ||
| Avoid CSS expressions CSS expressions (supported in IE beginning with Version 5) are a powerful, and dangerous, way to dynamically set CSS properties. These expressions are evaluated frequently: when the page is rendered and resized, when the page is scrolled, and even when the user moves the mouse over the page. These frequent evaluations degrade the user experience. |
Low | |
| No improvement suggestion available. Good job! | ||
| Make JavaScript and CSS external Using external JavaScript and CSS files generally produces faster pages because the files are cached by the browser. JavaScript and CSS that are inlined in HTML documents get downloaded each time the HTML document is requested. This reduces the number of HTTP requests but increases the HTML document size. On the other hand, if the JavaScript and CSS are in external files cached by the browser, the HTML document size is reduced without increasing the number of HTTP requests. |
N/A |
Medium |
|
Only consider this if your property is a common user home page.
|
||
| Reduce DNS lookups The Domain Name System (DNS) maps hostnames to IP addresses, just like phonebooks map people's names to their phone numbers. When you type URL www.yahoo.com into the browser, the browser contacts a DNS resolver that returns the server's IP address. DNS has a cost; typically it takes 20 to 120 milliseconds for it to look up the IP address for a hostname. The browser cannot download anything from the host until the lookup completes. |
Low | |
|
The components are split over more than 4 domains
|
||
| Minify JavaScript and CSS Minification removes unnecessary characters from a file to reduce its size, thereby improving load times. When a file is minified, comments and unneeded white space characters (space, newline, and tab) are removed. This improves response time since the size of the download files is reduced. |
Medium | |
|
There are 2 components that can be minified
|
||
| Avoid URL redirects URL redirects are made using HTTP status codes 301 and 302. They tell the browser to go to another location. Inserting a redirect between the user and the final HTML document delays everything on the page since nothing on the page can be rendered and no components can be downloaded until the HTML document arrives. |
Medium | |
| No improvement suggestion available. Good job! | ||
| Remove duplicate JavasScript and CSS Duplicate JavaScript and CSS files hurt performance by creating unnecessary HTTP requests (IE only) and wasted JavaScript execution (IE and Firefox). In IE, if an external script is included twice and is not cacheable, it generates two HTTP requests during page loading. Even if the script is cacheable, extra HTTP requests occur when the user reloads the page. In both IE and Firefox, duplicate JavaScript scripts cause wasted time evaluating the same scripts more than once. This redundant script execution happens regardless of whether the script is cacheable. |
Medium | |
| No improvement suggestion available. Good job! | ||
| Configure entity tags (ETags) Entity tags (ETags) are a mechanism web servers and the browser use to determine whether a component in the browser\'s cache matches one on the origin server. Since ETags are typically constructed using attributes that make them unique to a specific server hosting a site, the tags will not match when a browser gets the original component from one server and later tries to validate that component on a different server. |
Low | |
| No improvement suggestion available. Good job! | ||
| Make AJAX cacheable One of AJAX's benefits is it provides instantaneous feedback to the user because it requests information asynchronously from the backend web server. However, using AJAX does not guarantee the user will not wait for the asynchronous JavaScript and XML responses to return. Optimizing AJAX responses is important to improve performance, and making the responses cacheable is the best way to optimize them. |
Medium | |
| No improvement suggestion available. Good job! | ||
| Use GET for AJAX requests When using the XMLHttpRequest object, the browser implements POST in two steps: (1) send the headers, and (2) send the data. It is better to use GET instead of POST since GET sends the headers and the data together (unless there are many cookies). IE's maximum URL length is 2 KB, so if you are sending more than this amount of data you may not be able to use GET. |
Low | |
| No improvement suggestion available. Good job! | ||
| Reduce the number of DOM elements A complex page means more bytes to download, and it also means slower DOM access in JavaScript. Reduce the number of DOM elements on the page to improve performance. |
Low | |
|
There are 1081 DOM elements on the page
|
||
| Avoid HTTP 404 (Not Found) error Making an HTTP request and receiving a 404 (Not Found) error is expensive and degrades the user experience. Some sites have helpful 404 messages (for example, "Did you mean ...?"), which may assist the user, but server resources are still wasted. |
Medium | |
| No improvement suggestion available. Good job! | ||
| Reduce cookie size HTTP cookies are used for authentication, personalization, and other purposes. Cookie information is exchanged in the HTTP headers between web servers and the browser, so keeping the cookie size small minimizes the impact on response time. |
Low | |
| No improvement suggestion available. Good job! | ||
| Use cookie-free domains When the browser requests a static image and sends cookies with the request, the server ignores the cookies. These cookies are unnecessary network traffic. To workaround this problem, make sure that static components are requested with cookie-free requests by creating a subdomain and hosting them there. |
Low | |
| No improvement suggestion available. Good job! | ||
| Avoid AlphaImageLoader filter The IE-proprietary AlphaImageLoader filter attempts to fix a problem with semi-transparent true color PNG files in IE versions less than Version 7. However, this filter blocks rendering and freezes the browser while the image is being downloaded. Additionally, it increases memory consumption. The problem is further multiplied because it is applied per element, not per image. |
Medium | |
| No improvement suggestion available. Good job! | ||
| Do not scale images in HTML Web page designers sometimes set image dimensions by using the width and height attributes of the HTML image element. Avoid doing this since it can result in images being larger than needed. For example, if your page requires image myimg.jpg which has dimensions 240x720 but displays it with dimensions 120x360 using the width and height attributes, then the browser will download an image that is larger than necessary. |
Low | |
| No improvement suggestion available. Good job! | ||
| Make favicon small and cacheable A favicon is an icon associated with a web page; this icon resides in the favicon.ico file in the server's root. Since the browser requests this file, it needs to be present; if it is missing, the browser returns a 404 error (see "Avoid HTTP 404 (Not Found) error" above). Since favicon.ico resides in the server's root, each time the browser requests this file, the cookies for the server's root are sent. Making the favicon small and reducing the cookie size for the server's root cookies improves performance for retrieving the favicon. Making favicon.ico cacheable avoids frequent requests for it. |
Low | |
|
Favicon is not cacheable
|
||
WSZScore Analysis
| Parameter | Grade/Value | Severity |
|---|---|---|
| HTTP Status Code Last received HTTP code |
High | |
| HTTP Code should be 200. Code received: 200 | ||
| Total Transfer Time Total transaction time in seconds for last transfer |
High | |
| Total time of trasfer should be less than a 500 milliseconds. This trasfer contains only the HTML code excluding images, external css and js files. Transfer time recorded: 0.355929 sec. | ||
| DNS Lookup Time Time in seconds until name resolving was complete |
High | |
| Total time of DNS lookup should be less than a 30 milliseconds. Lookup time recorded: 0.029901 sec. | ||
| Connection Time Time in seconds it took to establish the connection |
High | |
| Total time before a connection is established should be less than a 10 milliseconds. Connection time recorded: 0.039779 sec. | ||
| Start Transfer Time Time in seconds until the first byte is about to be transferred |
High | |
| Total time before first byte is transferred should be less than a 100 milliseconds. Start Transfer time recorded: 0.334207 sec. | ||
| Redirect Time Time in seconds of all redirection steps before final transaction was started |
0 sec | Medium |
| Document Retrieve Time Remote time of the retrieved document, if -1 is returned the time of the document is unknown |
-1 sec | Medium |
| Pre Transfer Time Time in seconds from start until just before file transfer begins |
0.039785 sec | Medium |
| Upload Size Total number of bytes uploaded |
0 bytes | Low |
| Download Size Total number of bytes downloaded |
13606 bytes | Medium |
| Effective URL URL effected or used in the last CURL transfer. |
http://www.youtube.com/ | Medium |
| Download Speed Average download speed |
38226 bytes/sec | Medium |
| Upload Speed Average upload speed |
0 bytes/sec | Low |
| Header Size Total size of all headers received |
286 bytes | Medium |
| Request Size Total size of issued requests, currently only for HTTP request |
2464 bytes | Medium |
| Content Length Downloaded content-length of download, read from Content-Length: field |
13606 bytes | Medium |
| Content Length Uploaded Specified size of upload |
0 bytes | Low |
| Content Type Content-Type: of downloaded object, NULL indicates server did not send valid Content-Type: header |
text/html; charset=utf-8 | Low |
Waterfall View of the page The HTTP Archive(HAR) provides information about website performance such as # of HTTP requests, use of gzip, and amount of JavaScript. These can be used to analyze the issues such as 404 header response codes or external scripts load times, etc.
The HTTP Archive(HAR) provides information about website performance such as # of HTTP requests, use of gzip, and amount of JavaScript. These can be used to analyze the issues such as 404 header response codes or external scripts load times, etc. This HAR file is programatically generated for viewing purpose only. The orginal HAR file used is not avaliable to download/view because of security reasons.
TraceRoute for the domain traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. Traceroute sends a sequence of Internet Control Message Protocol (ICMP) echo request packets addressed to a destination host. Determining the intermediate routers traversed involves adjusting the time-to-live (TTL), aka hop limit, Internet Protocol parameter.
traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. Traceroute sends a sequence of Internet Control Message Protocol (ICMP) echo request packets addressed to a destination host. Determining the intermediate routers traversed involves adjusting the time-to-live (TTL), aka hop limit, Internet Protocol parameter. | Hop | Host | IP | Time#1 | Time#2 | Time#3 |
|---|
