Zoompf Mini Performance AssessmentThis is a free mini web performance assessment from Zoompf. To see Zoompf's full line of web performance optimization products and services, please visit http://zoompf.com/products.
Scan For: Performance Scan - 8/8/2010 1:21:15 PM
| Visited URLs | 77 |
| Pending URLs | 0 |
| Total Issues | 56 |
| Issues per URL | 0.73 |
| Start Time | 8/8/2010 1:21:15 PM |
| End Time | 8/8/2010 1:21:21 PM |
- High impact
- Easy to solve
URLs with Issue: 1
This external style sheet contains a single @import directive to include another style sheet. This causes the browser to make an additional HTTP requests to retrieve the additional sheet. Since this CSS file contains only a single @import you have should include the contents of imported style sheet in the base style sheet. This will reduce the number of HTTP requests required to load the web page improving page load times and decrease bandwidth consumption.
- High impact
- Easy to solve
URLs with Issue: 2
The resource was delivered by the web server using HTTP compression even though this resource's native format is already compressed. Since this resource was already compressed, using HTTP compression to transmit the resource adds overhead without reducing the size of the data to send to the client. Worse compressing already compressed data can actually increase the size of a resource due to the overhead of additional dictionaries, error checksums, etc. Examples of resources that are already compressed and should not be served using HTTP compression include images (GIF, JPG, PNG, etc) and ZIP files. Solving this issue will reduce bandwidth consumption and server resources while improving page load times.
- High impact
- Easy to solve
URLs with Issue: 52
The response for this image contains no HTTP caching information that allows it to be unconditionally cached on the client. HTTP caching can be used to instruct visitors to store a copy of the image on their systems for a long period of time. This is a valuable optimization for static content like images which do not change often. Using HTTP caching for this image will reduce the load on the web server, while significantly reducing both bandwidth consumption and page load times.
- High impact
- Easy to solve
URLs with Issue: 7
The response for this JavaScript file contains no HTTP caching information that allows it to be unconditionally cached on the client. HTTP caching can be used to instruct visitors to store a copy of the JavaScript file on their systems for a long period of time. This is a valuable optimization for static content like JavaScript files which do not change often. Using HTTP caching for this object will reduce the load on the web server, while significantly reducing both bandwidth consumption and page load times.
- High impact
- Easy to solve
URLs with Issue: 7
The response for this style sheet contains no HTTP caching information that allows it to be unconditionally cached on the client. HTTP caching can be used to instruct visitors to store a copy of the style sheet on their systems for a long period of time. This is a valuable optimization for static content like style sheets which do not change often. Using HTTP caching for this style sheet will reduce the load on the web server, while significantly reducing both bandwidth consumption and page load times.
- High impact
- Easy to solve
URLs with Issue: 2
This animated GIF image can be further optimized to reduce the file size without reducing image quality. This will improve server performance while decreasing bandwidth consumption.
The savings table details how much savings there is in optimizing these resources. We achieved these savings by using gifsicle to optimize the animated GIF.
| URL | Original Size | Optimized Size | Savings |
|---|---|---|---|
| http://feeds2.feedburner.com/~fc/smartpassiveincome?bg=FFFFFF&fg=444444&anim=0 | 1,204 | 394 | 67.276% |
| http://www.smartpassiveincome.com/wp-content/plugins/digg-digg/image/ajax-loader.gif | 8,787 | 8,668 | 1.354% |
| Average Savings: | 9.298% |
- High impact
- Easy to solve
URLs with Issue: 3
This GIF image contains extra data such as comments and unused palette entries and also uses an older graphics compression technology. This image can be further optimized using free tools that will reduce the size of the file without changing or reducing the image quality. These image optimizations are especially important as other optimizations, such as HTTP compression, cannot be applied to images. Optimizing this image will improve server performance while decreasing bandwidth consumption and page load times.
The savings table details how much savings there is in optimizing these resources. We achieved these savings by converting the GIF images to a PNG using gif2png and running pngcrush.
| URL | Original Size | Optimized Size | Savings |
|---|---|---|---|
| http://www.aweber.com/banners/email_marketing_easy/125x125.gif | 9,162 | 7,716 | 15.783% |
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/themes/greenbach2/images/sharethis-icons.gif | 1,467 | 1,125 | 23.313% |
| http://www.smartpassiveincome.com/wp-content/plugins/cforms/styling/captcha_reset_grey.gif | 461 | 454 | 1.518% |
| Average Savings: | 16.186% |
- High impact
- Easy to solve
URLs with Issue: 20
This JPG image can be further optimized to reduce the file size without reducing image quality. This will improve server performance while decreasing bandwidth consumption.
The savings table details how much savings there is in optimizing these resources. We achieved these savings by using jpegtran to optimize the JPEG image.
- High impact
- Easy to solve
URLs with Issue: 12
This PNG image is needlessly large. This is due to extra data inside the PNG file such as comments or unused palette entries as well as the use of an inefficient DEFLATE compressor. This image can optimized using free tools that would reduce the size of the file without changing or reducing the image quality. These image optimizations are especially important as other optimizations, such as HTTP compression, cannot be applied to images. Optimizing this PNG image will improve server performance while decreasing bandwidth consumption and page load times.
The savings table details how much savings there is in optimizing these resources. We achieved these savings by using pngcrush to optimize the PNG image.
- High impact
- Easy to solve
URLs with Issue: 7
This JPG image is needlessly large. By converting this JPG to a progressively rendered JPG you can reduce the size of the file without lossing image quality.This will improve server performance while decreasing bandwidth consumption.
The savings table details how much savings there is in optimizing these resources. We achieved these savings by using jpegtran to convert the image to a progressive JPEG image.
| URL | Original Size | Optimized Size | Savings |
|---|---|---|---|
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/themes/greenbach2/images/passive-income.jpg | 64,884 | 42,256 | 34.875% |
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/uploads/2008/12/time-money-relationship.jpg | 80,518 | 55,686 | 30.840% |
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/uploads/2010/07/explosive-targeted-traffic.jpg | 59,490 | 38,327 | 35.574% |
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/themes/greenbach2/images/about-box-video.jpg | 32,981 | 13,438 | 59.255% |
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/uploads/2009/06/passive-income-topics-closer-look.jpg | 86,437 | 50,088 | 42.053% |
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/themes/greenbach2/images/ia-preview.jpg | 48,920 | 24,454 | 50.012% |
| http://www.smartpassiveincome.com/images/how-to-make-iphone-apps.jpg | 42,948 | 21,231 | 50.566% |
| Average Savings: | 41.016% |
- High impact
- Challenging to solve
URLs with Issue: 1
This HTML page contains a set of separate yet sequential images and hyperlinks. Each image requires a separate HTTP request which increases the load time for this page. This series of <IMG> and <A> tags could all be combined into a client-side image map consisting of a single image with an <IMG> tag and a <MAP> tag. Creating a client-side image map will reduce the number of HTTP requests need to load this web page. This optimization will increase client and server side performance while reducing web server load and decrease bandwidth consumption.
- High impact
- Challenging to solve
URLs with Issue: 1
This web page contains multiple <SCRIPT SRC> tag which reference external JavaScript files on the same hostname and sometimes even in the same directory. As such it appears many of these external JavaScript files can be safely combined into a single JavaScript file. By combining multiple external JavaScript files into a single JavaScript file you will reduce the number of HTTP requests the browser has to make to render this web page. Combining these JavaScript files can drastically improve web server performance and page load times while reducing bandwidth consumption.
- High impact
- Challenging to solve
URLs with Issue: 1
This web page contains multiple <LINK> tags which reference external Cascading Style Sheets. These Cascading Style Sheets can be safely combined into only a handful of Cascading Style Sheets files. By combining multiple CSS files into a single CSS file you will reduce the number of HTTP requests the browser has to make to render this web page. Combining these CSS files will drastically improve web server performance and page load times while reducing bandwidth consumption.
- High impact
- Challenging to solve
URLs with Issue: 1
This HTML page closed a persistent connection. Persistent connections allow a web browser to download multiple resources without having to reestablish TCP and HTTP connections. While server will close persistent connections they should not do so on HTML pages because when an HTML page is requested the browser will most likely make subsequent requests for the resources on the page.
- High impact
- Challenging to solve
URLs with Issue: 1
This RSS Feed is not using the <skipDays> tag. The <skipDays> tag allows authors to define days for a blackout periods when they know they will not be posting new content. Common blackout days are Saturday and Sunday as people or businesses typically do not publish new content over the weekend. News readers will not request the RSS feed during these blackout days. This can lower the amount of bandwidth used to serve you feeds.
- High impact
- Challenging to solve
URLs with Issue: 1
This RSS Feed is not using the <skipHours> tag. The <skipHours> tag allows authors to define blackout periods when they know they will not be posting new content. A common blackout period is 12:00am to 6:00am as people or businesses typically do not publish new content in the middle of the night. News readers will not request the RSS feed during these blackout periods. This can lower the amount of bandwidth used to serve you feeds.
- High impact
- Challenging to solve
URLs with Issue: 1
This RSS Feed does not use a Time To Live (<ttl>) tag. The <ttl> tag instructs News clients how long to wait before checking requesting the RSS Feed again. Using a <ttl> tag can drastically lower bandwidth especially if the RSS feed is only updated a few times a day or week.
- High impact
- Difficult to solve
URLs with Issue: 1
This resource contains style information will too many individual background images. The browser must make an HTTP request for each background image that is used when rendering the web page. It is not uncommon for over half of all HTTP requests made for page resources to be for CSS background images. You can combine nearly all these background images into a handful of CSS Sprites. This will reduce the number of HTTP requests required to load this page which can significantly improve page load times while reducing web server load and bandwidth consumption.
- High impact
- Difficult to solve
URLs with Issue: 2
This JavaScript file appears to have been dynamically generated by the website's application tier. This is a common way to automatically minify or combine JavaScript files. However, invoking the application's logic to dynamically create this JavaScript file can be up to 10 times slower than simply serving a static file from the web server's file system. By dynamically generating this JavaScript file offline and then serving the static file you will reduce web server load and improve website performance.
- High impact
- Difficult to solve
URLs with Issue: 1
This page does not use multiple domain names to take advantage of parallel downloading. Parallel downloading allows the browser to download all the resources that make up a web page faster by downloading them in parallel from multiple hostnames. This will improve page load times.
- Medium impact
- Easy to solve
URLs with Issue: 1
This response for a resource (JavaScript file, CSS file, image, object, etc) is using the private caching directive in the Cache-Control HTTP header. The private caching directive means this response can only be cached by a specific user's browser and not by any shared upstream caches such as an ISP or corporate cache. Since this resource contains no personal, confidential, or user specific information there is no reason to use the private caching directive for this response. Removing the private caching directive will allow this resource to be cached which will decrease bandwidth consumption and web server load while improving page load times.
- Medium impact
- Easy to solve
URLs with Issue: 1
A web page contains commented out HTML code. This commonly occurs when a web developer someone wants to hide an old feature or content while still preserving a copy of it for later. While this is helpful to the web developer it harms the performance of the web page as this unused HTML code increases the size of the web page without improving the user experience. You should remove the commented out HTML code or alter it so it no longer appears in the HTML content which is sent to the visitor. This solution will improve page load time while reducing file size and bandwidth consumption.
- Medium impact
- Easy to solve
URLs with Issue: 1
This webpage contains numerous HTML tags that use the style attribute to convey styling information for that specific tag. Over 15 of these HTML tags contain the same CSS information in the style attribute. You should move this common CSS information out of multiple style attributes and into a reusable CSS class rule. This will make easier and more manageable to alter the style of this web page later and will also reduce this size of this web page. This solution will decrease bandwidth consumption and improve page load times.
- Medium impact
- Easy to solve
URLs with Issue: 7
This style sheet contains style information that has not been minified. Minifying style information reduces the size of the style information by removing whitespace and comments allowing for faster download and parsing. This improves page load time and decreases bandwidth consumption.
The savings table details how much savings there is in optimizing these resources. We achieved these savings by using CSS minification.
| URL | Original Size | Optimized Size | Savings |
|---|---|---|---|
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/themes/greenbach2/style.css.gzip | 20,162 | 18,582 | 7.837% |
| http://www.smartpassiveincome.com/wp-content/plugins/gregs-threaded-comment-numbering/gtcn-css.css?ver=1.4.2 | 238 | 223 | 6.303% |
| http://www.smartpassiveincome.com/wp-content/plugins/digg-digg/css/diggdigg-style.css?ver=4.2 | 3,213 | 2,656 | 17.336% |
| http://www.smartpassiveincome.com/wp-content/plugins/tubepress/ui/gallery/css/tubepress.css | 3,172 | 2,656 | 16.267% |
| http://www.smartpassiveincome.com/wp-content/plugins/cforms/styling/cforms.css | 9,635 | 6,387 | 33.710% |
| http://www.smartpassiveincome.com/wp-content/plugins/fidgetr/themes/theme_includes/crossfade/crossfade_fidgetr.css?ver=3.0.1 | 3,211 | 3,024 | 5.824% |
| http://www.smartpassiveincome.com/wp-content/plugins/cforms/styling/calendar.css | 2,222 | 1,862 | 16.202% |
| Average Savings: | 15.442% |
- Medium impact
- Easy to solve
URLs with Issue: 1
A large HTML comment was detected on this web page. HTML comments are not displayed or shown to a user, nor or they processed by Search engine spiders. As such, they add to the size of the page without adding any user experience or SEO value. HTML comments are often used with templating systems. Large HTML comments should be removed to improve page load time while reducing file size and bandwidth consumption.
- Medium impact
- Easy to solve
URLs with Issue: 27
This JPEG image was saved with a quality setting greater than 80. JPEG images use a variable level of quality, the higher the number the greater the quality but the larger the file size. However this setting can be deceptive. A quality rating of 90 does not mean "keep 90% of the graphical data." The quality scale is purely arbitrary; it's not a percentage of anything. A general guideline for JPEG images on the web is to use a quality rating of 50-75. This quality range is a good compromise between image quality and file size. Reducing this high quality JPEG will reduce file size, which will decrease bandwidth consumption and improve page load times.
The savings table details how much savings there is in optimizing these resources. We achieved these savings by reducing the quality of the JPEG image to 70.
- Medium impact
- Easy to solve
URLs with Issue: 1
This web page contains <IMG> tags which are not using height or width attributes. If the browser knows the height and width of an image before it downloads and renders the image it can continue to render the web page. If the browser does not know the image size it must redraw the web page again after the image downloads. Adding height or width attributes will make this web page render faster.
- Medium impact
- Easy to solve
URLs with Issue: 3
The response for this image contains HTTP caching information that allows it to be unconditionally cached on the client. However, this HTTP caching information instructs a visitor's browser to store the image for less than 4 months. Static content like images should be cached until a far future date, typically 6 months to a year, as it rarely changes and when it does change the content's URL changes as well. Using HTTP caching with this image for a date far into the future will reduce the load on the web server, while significantly reducing both bandwidth consumption and page load times.
- Medium impact
- Easy to solve
URLs with Issue: 28
This response contains an HTTP Vary header. The Vary header tells shared caches what information was used by the web server to gerenate the response. Because the server is using the browser identification string contained in the User-Agent head the ability of shared caches to serve this response to other users is drastically reduced. Removing the User-Agent value from the Vary and from the server's page generation logic allows efficent shared caching of this response, drastically reducing web server load.
- Medium impact
- Easy to solve
URLs with Issue: 3
This page contains JavaScript code that has not been minified. Minifying JavaScript reduces the size of the JavaScript allowing the browser to download, parse, and execute the code faster. This will improve application performance by decreasing page load time, bandwidth consumption, and web server load.
The savings table details how much savings there is in optimizing these resources. We achieved these savings by using JSMin to minify the JavaScript.
| URL | Original Size | Optimized Size | Savings |
|---|---|---|---|
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/themes/greenbach2/niftycube.js.gzip | 8,665 | 6,635 | 23.428% |
| http://www.smartpassiveincome.com/wp-content/plugins/cforms/js/cforms.js | 16,644 | 15,686 | 5.756% |
| http://www.smartpassiveincome.com/wp-content/plugins/tubepress/ui/lib/tubepress.js | 9,737 | 6,143 | 36.911% |
| Average Savings: | 18.781% |
- Medium impact
- Easy to solve
URLs with Issue: 2
The response for this JavaScript file contains HTTP caching information that allows it to be unconditionally cached on the client. However, this HTTP caching information instructs a visitor's browser to store the JavaScript file for less than 4 months. Static content like JavaScript files should be cached until a far future date, typically 6 months to a year, as it rarely changes and when it does change the content's url changes as well. Using HTTP caching with this JavaScript file for a date far into the future will reduce the load on the web server, while significantly reducing both bandwidth consumption and page load times.
- Medium impact
- Easy to solve
URLs with Issue: 3
The URL for this CSS file contains a query string. Query strings are not typically needed when serving static resources like images, style sheets, or scripts. HTTP caches typically will not cache any resource whose URL contains a query string. Removing the query string from the resource's URL will allow caching proxies or load balancers that you own and downstream caching proxies to serve this resource for you significantly reducing web server load and bandwidth consumption.
- Medium impact
- Easy to solve
URLs with Issue: 2
The URL for this image contains a query string. Query strings are not typically needed when serving static resources like images, style sheets, or scripts. HTTP caches typically will not cache any resource whose URL contains a query string. Removing the query string from the resource's URL will allow caching proxies or load balancers that you own and downstream caching proxies to serve this resource for you significantly reducing web server load and bandwidth consumption.
- Medium impact
- Easy to solve
URLs with Issue: 3
The URL for this JavaScript file contains a query string. Query strings are not typically needed when serving static resources like images, style sheets, or scripts. HTTP caches typically will not cache any resource whose URL contains a query string. Removing the query string from the resource's URL will allow caching proxies or load balancers that you own and downstream caching proxies to serve this resource for you significantly reducing web server load and bandwidth consumption.
- Medium impact
- Easy to solve
URLs with Issue: 1
This page contains a reference to a external JavaScript file in a suboptimal location. Specifically it contains a <SCRIPT SRC> tag that is not in the bottom 20% of the HTML. Browsers stop drawing the page and will not download any other files when they encounter JavaScript code. Moving <SCRIPT SRC> tags to the bottom of the web page will improve client-side performance.
- Medium impact
- Challenging to solve
URLs with Issue: 2
This web page contains HTML that has not been minified. HTML can contain extra whitespace, comments, unrecognized HTML tags, unminified JavaScript code in <SCRIPT> tags, and unminified CSS data in <STYLE> tags. For this web page, minifying the HTML will reduce the size of the page by more than 5%. Since this appears to be a dynamically generated web page, you should minify the template used by your application for this page. This solution will reduce bandwidth consumption while improving page load times.
The savings table details how much savings there is in optimizing these resources. We achieved these savings by minimizing the HTML by removing comments and whitespace and minifying any JavaScript or CSS blocks.
| URL | Original Size | Optimized Size | Savings |
|---|---|---|---|
| http://www.smartpassiveincome.com/ | 77,561 | 70,247 | 9.430% |
| http://twittercounter.com/embed/PatFlynn/626262/f2f2f2 | 344 | 0 | 100.000% |
| Average Savings: | 9.830% |
- Medium impact
- Challenging to solve
URLs with Issue: 5
This true color PNG image contains less than 2500 distinct colors. Converting this image from a true color PNG to a palette-based PNG (also called a PNG8) should significantly reduce the size of the image. While PNG8 will not have as many distinct colors as the original image this difference is not usually noticeable for images with less than 2500 distinct colors. Converting this image to a PNG8 will reduce bandwidth consumption and improve page load speeds.
The savings table details how much savings there is in optimizing these resources. We achieved these savings by converting this image to a PNG8 using pngquant.
| URL | Original Size | Optimized Size | Savings |
|---|---|---|---|
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/uploads/2008/11/comment_exclamation.png | 8,047 | 4,630 | 42.463% |
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/uploads/2009/09/dollar-sign.png | 58,850 | 6,464 | 89.016% |
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/uploads/2010/07/spi-artwork-rounded-200.png | 29,840 | 15,278 | 48.800% |
| http://d2gr0rrkrkzk97.cloudfront.net/wp-content/uploads/2010/07/subscribers-magnet.png | 32,494 | 12,798 | 60.614% |
| http://www.smartpassiveincome.com/images/bloggers-guide-facebook.png | 11,599 | 5,824 | 49.789% |
| Average Savings: | 68.051% |
- Medium impact
- Challenging to solve
URLs with Issue: 8
This true color PNG image has a pixel area less than 100 pixels by 100 pixels. Converting this image from a true color PNG to a palette-based PNG (also called a PNG8) should significantly reduce the size of the image. While PNG8 will not have as many distinct colors as the original image this difference should not be noticeable on such a small sized image. Converting this image to a PNG8 will reduce bandwidth consumption and improve page load speeds.
The savings table details how much savings there is in optimizing these resources. We achieved these savings by converting this image to a PNG8 using pngquant.
| URL | Original Size | Optimized Size | Savings |
|---|---|---|---|
| http://d2gr0rrkrkzk97.cloudfront.net/favicon.ico.gzip | 3,240 | 2,323 | 28.302% |
| http://www.smartpassiveincome.com/images/twitter_32.png | 2,324 | 1,787 | 23.107% |
| http://www.smartpassiveincome.com/images/technorati_32.png | 1,896 | 1,783 | 5.960% |
| http://www.smartpassiveincome.com/images/stumbleupon_32.png | 2,147 | 1,837 | 14.439% |
| http://www.smartpassiveincome.com/images/sm-youtube.png | 4,675 | 1,789 | 61.733% |
| http://www.smartpassiveincome.com/wp-content/plugins/digg-digg/image/comments-count.png | 3,265 | 350 | 89.280% |
| http://www.smartpassiveincome.com/wp-content/plugins/cforms/styling/li-err-bg.png | 250 | 131 | 47.600% |
| http://www.smartpassiveincome.com/wp-content/plugins/digg-digg/image/comments-link.png | 3,763 | 812 | 78.421% |
| Average Savings: | 49.852% |
- Medium impact
- Difficult to solve
URLs with Issue: 1
This image appears to have been dynamically generated by the website's application tier. Dynamically generating an image using application logic is a common way to create thumbnail images for online photo galleries or catalog websites. However invoking the application's logic to dynamically draw or resize an image file can be up to 10 times slower than simply serving a static file from the web server's file system. Dynamically generated images also do not have performance related HTTP headers such as Last-Modified or Accept-Bytes. These headers allow for conditional HTTP GET requests and for resumable downloads, both of which improve web performance. You should consider drawing or resizing this image offline as a static image file and then serve the static image file instead of dynamically generating the image. This solution will reduce web server load and improve website performance.
- Low impact
- Easy to solve
URLs with Issue: 1
This web page contains a <SCRIPT> tag which loads an external JavaScript file but it does not use a defer attribute. Using the defer attribute is an easy way to enable parallel downloading of resource for older web browsers like Internet Explorer 7 and Firefox 3.1. If appropriate, you can use the defer attribute to tell the browser it does not need to stop and wait for this external script file to load before downloading or rendering more content. Care must be taken later <SCRIPT> blocks may use code in deferred <SCRIPT SRC> blocks. Solving this issue will improve page load times and client-side performance.
- Low impact
- Easy to solve
URLs with Issue: 1
This web page contains <SCRIPT> tags with JavaScript that are adjacent to each other. Since there is no other content between these multiple <SCRIPT> tags all of their content can be combined into a single <SCRIPT> tag. This solution will slightly reduce page size and bandwidth consumption.
- Low impact
- Easy to solve
URLs with Issue: 1
This page contains a <STYLE> block with style information that has not been minified. Minifying style information reduces the size of the content, allowing for faster download and parsing.
- Low impact
- Easy to solve
URLs with Issue: 1
ETag headers provide web developers with more control over caching web resources. Unfortunately the default values for ETags used by web servers cause problems with load balanced environments, compression and web caches, and overrides more efficient caching methods such as the Expires HTTP header. Unless you are doing something special with ETags consider removing them.
- Low impact
- Easy to solve
URLs with Issue: 1
This page contains a <SCRIPT> tag containing JavaScript code that has not been minified. Minifying JavaScript reduces the size of the JavaScript, allowing for faster download and parsing while decreasing bandwidth and server loads.
- Low impact
- Easy to solve
URLs with Issue: 1
This is a very small image (less than 4x4 pixels) that appears to be used as a place holder image. Place holder images are an obsolete way to control the layout of a page. Use CSS properties like padding, margin, height and width to control padding and place elements. Using CSS instead of place holder images will reduce the number of requests needed to load the page. This will decrease page load time, web server load, and bandwidth consumption.
- Low impact
- Easy to solve
URLs with Issue: 1
This web page contains a <LINK> tag that exposes a remote blog editting API. This API is used by desktop blog programs to remotely edit your online content. Unless you are using desktop software to edit your live production content you should remove this <LINK> tag. Removing the tag will decrease web page size and improve page load times.
- Low impact
- Easy to solve
URLs with Issue: 1
This web page contains a <LINK> tag that exposes a remote blog editting API for Windows Live Writer. This API is used by Windows Live Writer to remotely edit your online content. Unless you are using Windows Live Writer to edit your live production content you should remove this <LINK> tag. Removing the tag will decrease web page size and improve page load times.
- Low impact
- Easy to solve
URLs with Issue: 45
This resource uses an HTTP header that is not common or was unnecessary given the HTTP request. These are usually inserted for promotional or debugging purposes by the application tier, web server modules, or inline network devices such as load balancers. You can remove this extra an unnecessary HTTP header to slightly reduce bandwidth consumption.
- Low impact
- Easy to solve
URLs with Issue: 1
This web page contains a <META> tag using the http-equiv attribute to define the character set used for this web page. However the web server also using the HTTP Content-Type header to define the character set for this web page. Since the browser will ignore any character set information in a <META> tag if there is character set information present in the Content-Type header the <META> tag is unnecessary and can be removed. Removing the <META> tag will slightly reduce page size and bandwidth consumption.
- Low impact
- Easy to solve
URLs with Issue: 3
This response is using the HTTP header Pragma to attempt to control caching. Most caching proxies and some web browsers do not use the Pragma header to determine caching information. Since this response also uses the Expires or Cache-Control HTTP header the Pragma header is unnecessary. Removing the Pragma header from this response will slightly decrease bandwidth consumption.
- Low impact
- Challenging to solve
URLs with Issue: 1
This web page contains a large number of references and hyperlinks to resources on the same host using absolute URLs. Each absolute URLs includes the protocol, hostname, and port number as well as the typical path, filename, and query string information. Since this web page is referenced using the same protocol, hostname, and port number that the absolute URLs use these URLs can be converted from absolute URLs into relative URLs without any loss of functionality. This solution would reduce web page size and bandwidth consumption.
- Low impact
- Challenging to solve
URLs with Issue: 1
This page contains over eight <INPUT type="hidden"> tags. This increases the size of the web page as well as requests from the client for web form submissions. Consider removing or consolidating these fields into a smaller number of hidden inputs or store some of this data on the server in session oriented storage. This will decrease page load time and bandwidth consumption.
- Low impact
- Challenging to solve
URLs with Issue: 5
This resource contains JavaScript code that is using the eval() function. JavaScript's eval() function is used to dynamically compile and execute JavaScript code that is stored in a string. This process is expensive and generally it should be avoided. Avoiding the use of eval() will improve client-side performance.
- Low impact
- Challenging to solve
URLs with Issue: 1
JavaScript's setTimeout() function can be used to execute a JavaScript function after a certain amount of time. If you use pass a string to setTimeout() it must be dynamically compiled when used, which is a horrible performance hit. Pass a function to setTimeout() instead of a string.
- Low impact
- Difficult to solve
URLs with Issue: 3
The iPhone is only able to cache responses whose uncompressed size is less than 15 Kilobytes. This text response is between 15K and 20K. Minifying the text (removing whitespace, comments, etc) might reduce this response to be less than 15K. Reducing the size of this response so it is cachable on the iPhone will reduce web server load and improve page load speeds for iPhone visitors.
- Difficult to solve
URLs with Issue: 15
The iPhone is only able to cache web server responses whose uncompressed size is less than 15 Kilobytes. This response is greater than 20K. There is no easy way to make this response small enough to be cached by the iPhone. If this is an important resource that should be cached you should redesign the resource so it is small enough to be cached. Caching responses on the iPhone will reduce web server load and improve page load speeds for iPhone visitors.
