Tools & Wizards About Us
fanale.name screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fanale.name

Page Load Speed

27.2 sec in total

First Response

194 ms

Resources Loaded

26.1 sec

Page Rendered

831 ms

fanale.name screenshot

About Website

Welcome to fanale.name homepage info - get ready to check Fanale best content right away, or after learning these important things about fanale.name

Visit fanale.name

Key Findings

We analyzed Fanale.name page load time and found that the first response time was 194 ms and then it took 27 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 23 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

fanale.name performance score

0

Network Requests Diagram

fanale.name

194 ms

blog.fanale.name

4312 ms

serendipity.css

608 ms

nav.css

817 ms

s9y.css

813 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fanale.name, 43% (40 requests) were made to Blog.fanale.name and 25% (23 requests) were made to Static.technorati.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Static.technorati.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 391.8 kB (34%)

Content Size

1.2 MB

After Optimization

761.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fanale.name main page is 1.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 863.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 104.3 kB

  • Original 118.9 kB
  • After minification 112.0 kB
  • After compression 14.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 104.3 kB or 88% of the original size.

Image Optimization

-20%

Potential reduce by 172.9 kB

  • Original 863.0 kB
  • After minification 690.1 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Fanale needs image optimization as it can save up to 172.9 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 111.5 kB

  • Original 167.0 kB
  • After minification 152.7 kB
  • After compression 55.5 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 111.5 kB or 67% of the original size.

CSS Optimization

-69%

Potential reduce by 3.2 kB

  • Original 4.6 kB
  • After minification 3.5 kB
  • After compression 1.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Fanale.name needs all CSS files to be minified and compressed as it can save up to 3.2 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (65%)

Requests Now

63

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fanale. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fanale.name

fanale.name

194 ms

blog.fanale.name

blog.fanale.name

4312 ms

serendipity.css

serendipity.css

608 ms

nav.css

nav.css

817 ms

s9y.css

s9y.css

813 ms

jquery.js

jquery.js

1832 ms

overlib.js

overlib.js

2376 ms

tabber.css

tabber.css

3812 ms

urchin.js

urchin.js

62 ms

mlt.js

mlt.js

67 ms

jsserv.php

jsserv.php

56 ms

nitobi.replay.js

nitobi.replay.js

69 ms

mlt.js

mlt.js

203 ms

plusone.js

plusone.js

857 ms

icon-utag-16x13.png

icon-utag-16x13.png

19776 ms

en.worldbesthostels.com.png

en.worldbesthostels.com.png

9517 ms

smile.png

smile.png

532 ms

twitter.png

twitter.png

178 ms

delicious.png

delicious.png

1603 ms

facebook.png

facebook.png

1058 ms

googlebookmark.png

googlebookmark.png

325 ms

friendfeed.png

friendfeed.png

489 ms

diggman.png

diggman.png

626 ms

mixx-button4.png

mixx-button4.png

791 ms

bloglines.png

bloglines.png

1688 ms

technorati.png

technorati.png

949 ms

fark.png

fark.png

1047 ms

yahoomyweb.png

yahoomyweb.png

1194 ms

furl.png

furl.png

1261 ms

reddit.png

reddit.png

1317 ms

blinklist.png

blinklist.png

1347 ms

spurl.png

spurl.png

1445 ms

newsvine.png

newsvine.png

1462 ms

simpy.png

simpy.png

1564 ms

blogmarks.png

blogmarks.png

1584 ms

wists.png

wists.png

1614 ms

wong18.gif

wong18.gif

1695 ms

button0-bm.gif

button0-bm.gif

1726 ms

stumbleupon.gif

stumbleupon.gif

1730 ms

printfriendly.png

printfriendly.png

1740 ms

email_link.png

email_link.png

2520 ms

identica.png

identica.png

1837 ms

xml.gif

xml.gif

2585 ms

fbapix.gif

fbapix.gif

1897 ms

xml.gif

xml.gif

1903 ms

icon-utag-16x13.png

icon-utag-16x13.png

19743 ms

icon-utag-16x13.png

icon-utag-16x13.png

19743 ms

icon-utag-16x13.png

icon-utag-16x13.png

19743 ms

icon-utag-16x13.png

icon-utag-16x13.png

19743 ms

icon-utag-16x13.png

icon-utag-16x13.png

19742 ms

icon-utag-16x13.png

icon-utag-16x13.png

19743 ms

icon-utag-16x13.png

icon-utag-16x13.png

19742 ms

icon-utag-16x13.png

icon-utag-16x13.png

19742 ms

icon-utag-16x13.png

icon-utag-16x13.png

19743 ms

icon-utag-16x13.png

icon-utag-16x13.png

19742 ms

icon-utag-16x13.png

icon-utag-16x13.png

19743 ms

icon-utag-16x13.png

icon-utag-16x13.png

19742 ms

icon-utag-16x13.png

icon-utag-16x13.png

19743 ms

icon-utag-16x13.png

icon-utag-16x13.png

19744 ms

icon-utag-16x13.png

icon-utag-16x13.png

19743 ms

icon-utag-16x13.png

icon-utag-16x13.png

19743 ms

icon-utag-16x13.png

icon-utag-16x13.png

19746 ms

icon-utag-16x13.png

icon-utag-16x13.png

19747 ms

icon-utag-16x13.png

icon-utag-16x13.png

19748 ms

icon-utag-16x13.png

icon-utag-16x13.png

19747 ms

icon-utag-16x13.png

icon-utag-16x13.png

19748 ms

icon-utag-16x13.png

icon-utag-16x13.png

19748 ms

like.php

like.php

326 ms

like.php

like.php

402 ms

like.php

like.php

342 ms

like.php

like.php

338 ms

like.php

like.php

342 ms

Sh_BYjerrZ8.js

Sh_BYjerrZ8.js

1292 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

1401 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

299 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

205 ms

fastbutton

fastbutton

346 ms

fastbutton

fastbutton

342 ms

fastbutton

fastbutton

269 ms

fastbutton

fastbutton

243 ms

fastbutton

fastbutton

375 ms

stars-def-yellow-red-sm.png

stars-def-yellow-red-sm.png

1037 ms

wikipedia_black.gif

wikipedia_black.gif

1068 ms

rs=AGLTcCPnvMBJ32ao-vxx78giqcGO6TMjFw

rs=AGLTcCPnvMBJ32ao-vxx78giqcGO6TMjFw

135 ms

postmessageRelay

postmessageRelay

244 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

253 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

48 ms

__utm.gif

__utm.gif

58 ms

1077434459-postmessagerelay.js

1077434459-postmessagerelay.js

203 ms

rpc:shindig_random.js

rpc:shindig_random.js

119 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

71 ms

print.css

print.css

154 ms

SEO Factors

fanale.name SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanale.name can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Fanale.name main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

fanale.name

Open Graph description is not detected on the main page of Fanale. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: