06 Oktober 2010

Ayo Analisa Web Kita !


ada web menarik yang aku ketemu gak sengaja pas lagi keliling ke tetangga, eh jadi iseng deh pengen nyoba berhubung blog baruu harus di test, ini website yang namanya web page analyzer yang sesuai dengan kebutuhan jaman saat ini ketika harga BBM dan bahan pokok melunjak serta mengakibatkan demo dimana-dimana (ahayy berat banget masalah tanah air) web ini murni gratis..tis..tis

web page analyzer  ini yang bisa ngasih info mengenai kecepatan Load, Download Times, Global Static, dll. jadi kita bisa tahu apa sih yang dialamin sama pengakses blog kita, soalnya semua orang kan punya jaringan internet dan web browser yang beda-beda. dan kita juga bisa di analisisnya apa sih yang bikin weblog kita lelet atau berat.

Pengen nyoba? berikut langkah-langkahnya :
1. Buka situsnnya di http://analyze.websiteoptimization.com
2. Setelah terbuka, masukkan url link website anda masing-masing di Enter URL to diagnose.
3. Anda akan diminta untuk memasukkan kode captcha. Abis itu klik Continue
4. Setelah beberapa detik, akan muncul tuh seonggok informasi tentang website anda. Mulai dari Global Statistics, Object Size Totals, External Objects, Download Times, dan Page Objects.

sedikit bocorang tentang blog saya yang hasil analisanya mengenaskan dan saya bingung mau nghilangin yang mana, sayaang (ノ><)ノ

Diagnosis

Global Statistics

Total HTTP Requests:28
Total Size:618554 bytes

Object Size Totals

Object typeSize (bytes)Download @ 56K (seconds)Download @ T1 (seconds)
HTML:26028452.271.78
HTML Images:220015 46.65 3.97
CSS Images:49537 10.27 0.66
Total Images:269552 56.92 4.63
Javascript:71934 15.34 1.38
CSS:16784 4.15 0.89
Multimedia:0 0.00 0.00
Other:0 0.00 0.00

External Objects

External ObjectQTY
Total HTML:2
Total HTML Images:14
Total CSS Images:2
Total Images:16
Total Scripts:5
Total CSS imports:4
Total Frames:0
Total Iframes:2

Download Times*

Connection RateDownload Time
14.4K 485.01 seconds
28.8K 245.31 seconds
33.6K 211.06 seconds
56K 128.88 seconds
ISDN 128K 43.35 seconds
T1 1.44Mbps 8.88 seconds
*Note that these download times are based on the full connection rate for ISDN and T1 connections. Modem connections (56Kbps or less) are corrected by a packet loss factor of 0.7. All download times include delays due to round-trip latency with an average of 0.2 seconds per object. With 28 total objects for this page, that computes to a total lag time due to latency of 5.6 seconds. Note also that this download time calculation does not take into account delays due to XHTML parsing and rendering.

# Congratulations. This site is using HTTP compression, otherwise called content encoding using gzip. The sizes reported here are for compressed content sent from the server to the client.
* CSS alternate stylesheets may be referenced in the HTML but are not actually downloaded until they are needed and are therefore not included in the total page size.

Analysis and Recommendations

  • TOTAL_HTML - Congratulations, the total number of HTML files on this page (including the main HTML file) is 2 which most browsers can multithread. Minimizing HTTP requests is key for web site optimization. Y
  • TOTAL_OBJECTS - Warning! The total number of objects on this page is 28 which by their number will dominate web page delay. Consider reducing this to a more reasonable number. Above 20 objects per page the overhead from dealing with the actual objects (description time and wait time) accounts for more than 80% of whole page latency. See Figure II-3: Relative distribution of latency components showing that object overhead dominates web page latency in Website Optimization Secrets for more details on how object overhead dominates web page latency. Combine, refine, and optimize your external objects. Replace graphic rollovers with CSS rollovers to speed display and minimize HTTP requests. Consider using CSS sprites to help consolidate decorative images. Using CSS techniques such as colored backgrounds, borders, or spacing instead of graphic techniques can reduce HTTP requests. Replace graphic text headers with CSS text headers to further reduce HTTP requests. Finally, consider optimizing parallel downloads by using different hostnames or a CDN to reduce object overhead.
  • TOTAL_IMAGES - Caution. You have a moderate amount of images on this page (16 ). Consider using fewer images on the site or try reusing the same image in multiple pages to take advantage of caching. Using CSS techniques such as colored backgrounds, borders, or spacing instead of graphic techniques can help reduce HTTP requests.
  • TOTAL_CSS - Caution. The total number of external CSS files on this page is 4 , consider reducing this to a more reasonable number. Because external CSS files must be in the HEAD of your HTML document, they must load first before any BODY content displays. Although they are cached upon subsequent requests, CSS files slow down the initial display of your page. Combine, refine, and optimize your external CSS files. Ideally you should have one (or even embed CSS for high-traffic pages) on your pages. You can optimize CSS files using shorthand properties, grouping, and then minify and GZIP compress them to reduce their footprint. Remember to place CSS files in the HEAD and JavaScript files at the end of the BODY to enable progressive display.
  • TOTAL_SIZE - Warning! The total size of this page is 637782 bytes, which will load in 128.88 seconds on a 56Kbps modem. Consider reducing total page size to less than 100K to achieve sub 20 second response times on 56K connections. Pages over 100K exceed most attention thresholds at 56Kbps, even with feedback. Consider optimizing your site with Website Optimization Secrets, Speed Up Your Site or contacting us about our optimization services.
  • TOTAL_SCRIPTCaution The total number of external script files on this page is 5 , consider reducing this to one or two. Combine, refactor, and minify to optimize your JavaScript files. Ideally you should have one (or even embed scripts for high-traffic pages) on your pages. Consider suturing JavaScript files together at the server to minimize HTTP requests. Placing external JavaScript files at the bottom of your BODY, and CSS files in the HEAD enables progressive display in XHTML web pages.
  • HTML_SIZE - Warning! The total size of this HTML page is 260284 bytes, which is over 100K! Consider optimizing your HTML and eliminating unnecessary content and features. Recommend that you substitute abstract CSS rules for repeated embedded styles and eliminate as many comments and whitespace as possible. Using HTTP compression to compress your XHTML with GZIP can reduce your html by an average of 75%.
  • IMAGES_SIZE - Warning! The total size of your images is 269552 bytes, which is over 100K. Consider switch graphic formats to achive smaller file sizes (from JPEG to PNG for example). Finally, substitute CSS techniques for graphics techniques to create colored borders, backgrounds, and spacing.
  • SCRIPT_SIZE - Warning! The total size of external your scripts is 71934 bytes, which is over 20K. Consider optimizing your JavaScript for size, combining them, and using HTTP compression where appropriate for any scripts placed in the HEAD of your documents. You can substitute CSS menus for JavaScript-based menus to minimize or even eliminate the use of JavaScript.
  • CSS_SIZE - Caution. The total size of your external CSS is 16784 bytes, which is above 8K and less than 20K. For external files, ideally keep them less than 1160 bytes to fit within one higher-speed TCP-IP packet (or an approximate multiple thereof). Consider optimizing your CSS and eliminating features to reduce this to a more reasonable size.
  • MULTIM_SIZE - Congratulations, the total size of all your external multimedia files is 0 bytes, which is less than 10K.

Tidak ada komentar:

Posting Komentar

Variabel : KAMMI dan FH UB (Perspektif Saya) Kaitan Kepentingan

Saya ingin menulis sedikit tentang ketakutan tentang “kepentingan” yang berada di FH UB, ada sebuah statement menarik di ask.fm sesungguhny...